This is an overview of domain separation and Field Service Management. Domain
separation enables you to separate data, processes, and administrative tasks into logical
groupings called domains. You can then control several aspects of this separation, including
which users can see and access data.
Support: Level 1
Domain separation is
supported in this application. Not all ServiceNow applications support domain
separation; some include limitations on the data and administrative settings that can be
domain separated. To learn more, see Application support for domain
In the Field Service Management application, you can use the Company entity to drive domain
separation. Assign a domain to each company and then any work orders and tasks created for a
company are created within the company domain. Other entities and tasks related to work
orders, such as dispatcher and assignment groups, part requirements, and transfer orders,
are driven by the company and work order domains.
How domain separation works in Field Service Management
Domain separation for Field Service Management uses the Company entity to drive the domain
structure. To use domain separation, all companies must be assigned to a domain.
When using Field Service Management in a domain separated instance, the
Company field is a mandatory field on the Work Order form. When you
create a work order for a company, the work order is created in the company domain. Any
tasks created for the work order are also created in the company domain.
When using Field Service Management integrated with Customer Service Management in a domain
separated instance, the Account field is a mandatory field on the
Work Order form. When you create a work order for an account through a customer service
case, the work order is created in the account domain. Any tasks created for the work order
are created in the same domain as the work order. In the event that the domain of the work
order changes, the domain of the work order tasks is also updated.
Modifying the company or account on a work order also modifies the domain of the work order
and work order tasks. The domains of other related entities are not automatically updated.
The company or account can be changed until the work order is qualified.
Note: Field Service
Management is configured at the application level and does not support domain-specific
configuration. For example, if you select use dynamic scheduling as
your task assignment method, this method is used to assign tasks in all
Setting up domain separation in Field Service Management
To set up domain separation for Field Service Management, contact ServiceNow, Inc.
Work orders created from Incident, Problem, or Change
For work orders created from an incident, problem, or change request:
- The company on the work order is inherited from the original record.
- The domain of the work order is inherited from the company.
- If the original record does not include a company, the Company
field is still a required field on the Work Order form.
Qualification, dispatcher, and assignment groups are filtered based on the domain of the
work order and work order tasks. The group domain must match the work order or work order
The parts process, which includes sourcing and using assets, is also domain separated.
- Part requirements are created in the work order domain.
- Transfer orders and transfer order lines created for a part requirement are created in
the part requirement’s domain.
- Assets are available for a work order or work order task based on the part requirement
- When sourcing a part:
- Assets are available based on the part requirement domain.
- Stockrooms are available based on available assets.