This is an overview of domain separation and the Notifications application. 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.
Domain separation is specifically supported in Notifications but not in email accounts.
Notifications are not data-separated but they are process-separated. Notifications are also
triggered by specific actions.
How domain separation works in Notifications
There are two basic components of domain separation and Notifications.
- Notifications are process-separated (not data-separated).
- Notifications are triggered in two main ways:
- When a record is Inserted or Updated
- Notifications with matching conditions AND in the same domain as the
inserted/updated record are processed.
- When an event defined in the notification is triggered
- Events typically have a target record. For example, [incident.inserted] event
references the incident record being inserted.
- When an event is fired, notifications configured for that event in the same
domain as the event’s target record are processed.
Domains and email accounts
Domain separation is not supported in email accounts for these reasons:
- Sending mail: There is only one SMTP sender per account. This prohibits providing
domains for each account, and they are not configurable.
- For receiving Inbound mail: You can set up multiple email accounts but cannot
meaningfully set the domain of an inbound email action. Inbound Actions are processed in
the domain of the user who sent the email. For example: User_A in Domain A sends an
email to a ServiceNow email account which executes the “Create an incident” inbound
email action. The resulting new incident created by the inbound action is in Domain
A.
To learn more see
Inbound email actions.
Note: If the number of email accounts exceeds 20, reception of email slows down.
Use case
-
If an instance is using the
Domain separation plugin
and a new email notification is
defined for a domain that has the same event as the notification on the global domain,
the user receives two emails for the same event.
Solution: Set the [sys_overrides] field on the notification that belongs to the
domain so it overrides the setting on global. For more information, see
Delegated administration
.
