The topic includes an overview of domain separation and Problem 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.
Overview
Support: Level 2
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
separation.
- Problem Management is about eliminating
the root cause of a service interruption.
- The problem and problem task tables support domain separation. Therefore a Problem user sees
only problems or problem tasks that have been created within the (tenant) domain that they
belong to.
- Only Problem users can create and access Problems and problem tasks.
- Problem and problem task tables both support domain separation. Therefore, a Problem user
sees only problems and problem tasks that have been created within the (tenant) domain that
they belong to.
How domain separation works in Problem Management
Problem users see only problems and problem tasks that have been created within the (tenant)
domain that they belong to.
Problem users can use Problems and problem tasks within the tenant domains. Problem users can
create and update problems and problem tasks of their domain, any child domains, and the global
domain.
Known Issues
Task-Outage Relationship [cmdb_ci_outage] is not domain separated.
If installed, the Task-Outage Relationship table is not domain separated. Therefore Fulfillers
or Problem users can view any Task-Outage Relationship records regardless of the domain that the
records belong to.
The Task-Outage Relationship table is installed when administrator activates the optional
Task-Outage Relationship plugin.
To learn more, see the Task-Outage Relationship components and Activate Task-Outage Relationship topics.
