In Salesforce Field Service (SFS), when a Service Territory is created, Salesforce automatically creates and associates a Public Group with the same name as the Service Territory. This Public Group is used internally by Field Service for scheduling and dispatch operations.
When a user later tries to rename the Service Territory, Salesforce automatically attempts to update the name of the associated Public Group as well. If the user does not have the Manage Users system permission (which is required to rename Public Groups), the rename operation fails.
Non-admin users without this permission will encounter the following error:
FSL.TR0023_ServiceTerritory_BeforeAfterUpdate: execution of AfterUpdate caused by:
System.SObjectException: Field is not writeable: Group.Name (System Code)
This error is thrown by the Field Service managed package trigger FSL.TR0023_ServiceTerritory_BeforeAfterUpdate, which fires when a Service Territory record is updated. The trigger attempts to update the linked Public Group's name, but the user lacks the required permission to do so.
This behavior is by design in Salesforce Field Service.
Root Cause: Renaming a Service Territory triggers Salesforce to automatically rename the associated Public Group. The Manage Users system permission is required to update a Public Group's name (Group.Name field). Most service resource profiles and non-admin profiles do not include this permission by default.
Solution: Grant the Manage Users permission to users who need to rename Service Territories. This can be done via the user's Profile or a Permission Set.
The Manage Users permission is a powerful system-level permission that grants broad user management capabilities across the org. Evaluate your security model carefully before assigning this permission broadly. Consider limiting it to specific users or roles who genuinely need to rename Service Territories.
005104418

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.