This is an overview of domain separation as it pertains to Survey Management. Domain
separation allows 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: Data only
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
As a survey creator, survey_admin can create surveys in the assigned domain. A Global domain
survey_admin can create or edit survey in any domain.
As a survey taker, a user can access the survey record and take the survey based on the domain
of the survey record and user. Global domain users can take a survey in any domain.
How domain separation works in Survey Management
There are several main areas to consider in how domain separation works in Survey
Survey Management in domain separated instances
The following domains are available by default after activating the Domain Support-Domain
Extensions Installer [com.glide.domain.msp_extensions.installer] plugin. Only ServiceNow
employees can activate this plugin.
Access to surveys in domain-separated instances
Based on the domain of the survey record and users, users can access the survey record and
take the survey.
Global domain users can access survey records in any domain. Users in any other domain can
access records in their domain and in Global domain. For example, users in the Acme domain can
access records in the Acme domain and the Global domain.
Global domain users can take a survey in any domain. Users in any other domain can take
surveys in their domain as well as the Global domain. For example, users in Acme domain can take
surveys in the Acme domain and the Global domain.
|Location of the survey record
||Users who can access and take the
Any domain user can assign a survey in that domain to the same domain user or a Global domain
user. For example, an Acme domain user can assign a survey to a Global domain user or an Acme
domain user. Users from other domains are not visible to the Acme domain user.
Although the Global domain user can view a survey from other domains, this user cannot assign
the survey of one domain to a user from a different domain. For example, a Global domain user
can assign a survey from the Acme domain to another Global domain user or an Acme domain user,
but not to a Cisco domain user.
Note: When a task is closed in a child domain and the assigned survey is either in the child
domain or the Global domain, the user from the child domain can then take the survey.
Trigger conditions in domain-separated instances
A Global domain user can create a triggered condition for a survey from any domain. The Global
domain user can create an incident and trigger the survey by selecting a user from the other
domain in the User field under Caller. However,
the Global user cannot assign the survey to the user of different domain.
A user can assign a trigger condition to a survey if the user belongs to the Global domain or
the Survey domain.
If there is no domain path for a trigger condition, users from any domain can view the trigger
condition. For example, in the
asmt_condition table that has no column for the
domain path, users from the Acme domain can view the trigger condition created by the Cisco