Dispatcher Users Unable to View Service Territory Records

This behavior is by design. The automatic sharing mechanism that populates Territory Public Groups is only triggered when the OWD is Private for Service Territory, because that is the configuration for which the sharing job is relevant. https://help.salesforce.com/s/articleView?id=service.fs_territory_guidelines.htm&language=en_US&type=5

At the time of Service Territory creation, when OWD (Org-Wide Default) Sharing for Service Territory is set to Public. Any new Service Territories created under this setting will not be automatically shared with the public group.

If the OWD is later changed to Private, existing Service Territories will also not be automatically shared with the public group.

However, when the OWD is set to Private from the time of org creation, any new Service Territories created will be automatically shared with the public group.

Option 1 — Switch OWD to Private (Recommended)

1. Go to Setup → Sharing Settings.
2. Change the OWD for Service Territory to Private.
3. New Service Territory records will now be automatically shared with the Territory Public Groups, and Dispatcher users with User Territory assignments will gain access.

Option 2 — Manual Sharing (Temporary Workaround)

1. Open the Service Territory record.
2. Click Sharing (from the record's action menu or related list).
3. Manually add the relevant Dispatcher users or Territory Public Groups with the appropriate access level (Read Only or Read/Write).

Manual sharing is not a scalable long-term solution for large numbers of territories or users. Option 1 is the recommended approach for orgs using FSL's User Territory sharing model.

Draft Error Code / Message

No error message is displayed. The User Territories scheduled job completes successfully but with TotalJobItems: 0, meaning no sharing records are created.