---
sourceDocument: Brazil Field Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/field-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# Schedule Optimization integration user access requirements

# Schedule Optimization integration user access requirements {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Describes the access requirements for the shared integration user account used by Schedule Optimization.

## User access requirements {#schedule-optimization-integration-user-access-requirements__schedule-optimization-integration-user-access-requirements-section-1}

Schedule Optimization uses a dedicated service account `sharedservice.worker` to execute database queries during optimization. This account does not have admin access. Read access for all OOTB fields
on the work order task table is already granted to this account. However, if a Task Filter references a custom field, a custom table, or a table other than the default work order task table to submit work orders, you must grant the
`sharedservice.worker` account the admin role. If the role is not granted, affected tasks may be skipped during optimization, which can cause double booking or incorrect assignments.

To add the role, navigate to User AdministrationUsers, search by User ID for `sharedservice.worker`, and open the record. In the Roles related list, select Edit to add the roles required
to grant read access to the fields and tables referenced in your task filter.
**Related tasks**   

* [Create a scheduling attribute for Schedule Optimization](https://www.servicenow.com/docs/HXbBty8Ld4XVRftu9CjK_A "Create scheduling attributes to specify which tasks to optimize and define the rules to perform the optimization. You can create different scheduling attributes configurations for each policy.")

*[\>]: and then