/product-fieldpulse/b/product-news/posts/updated-changes-to-user-role-permissions-in-3-3With the release of FieldPulse 3.3, several changes were made to the user role permission system. This post clarifies those changes and provides guidance for administrators.What ChangedThe following permissions have been modified or relocated:Work Oren-US14.0.0.622 14https://verint14-pre-03.socialedgeconsulting.io/product-fieldpulse/b/product-news/posts/updated-changes-to-user-role-permissions-in-3-3Sun, 30 Nov 2025 19:10:00 GMTc4b96cc1-2109-42ea-ab24-296f0d9934d9Mike Dolan1<p>Why was Delete separated from Edit? Now I have to touch 40 user records.</p><img src="https://verint14-pre-03.socialedgeconsulting.io/aggbug?PostID=82^AppID=21^AppType=Weblog^ContentType=0" width="1" height="1">https://verint14-pre-03.socialedgeconsulting.io/product-fieldpulse/b/product-news/posts/updated-changes-to-user-role-permissions-in-3-3Sun, 30 Nov 2025 14:22:00 GMTc4b96cc1-2109-42ea-ab24-296f0d9934d9Anita Sharma1<p>Thank you for the clarification. I have reviewed our custom roles and identified two that require updates:</p><ol><li>Our &quot;Senior Technician&quot; role previously included Work Order &gt; Delete implicitly</li><li>Our &quot;Regional Manager&quot; role used the deprecated Dispatch &gt; Bulk Reassign permission</li></ol><p>I have confirmed that the automatic mapping is functioning as described. I will proceed with manual adjustments to align with our governance policy.</p><img src="https://verint14-pre-03.socialedgeconsulting.io/aggbug?PostID=82^AppID=21^AppType=Weblog^ContentType=0" width="1" height="1">