---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Domain separation and Notifications

# Domain separation and Notifications {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Domain separation is supported in the Notifications application. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

## Support level: Standard {#domain-separation-notifications__section_y3d_xvr_xkb}

* Includes all aspects of Basic level support.
* Application properties are domain-aware as needed.
* Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
* The instance owner must configure the minimum viable product (MVP) business logic and data parameters per tenant as expected for the specific application.
{#domain-separation-notifications__ul_tfh_drj_xkb}

Sample use case: An admin must be able to make comments required when a record closes for
one tenant, but not for another.{#domain-separation-notifications__p_ssc_nfg_h1c}

For more information on support levels, see [Application support for domain
separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US).{#domain-separation-notifications__p_tsc_nfg_h1c}

## Overview {#domain-separation-notifications__section_pvf_wkx_vcb}

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.  
Note:  
Subscription-based notifications are not domain aware and cannot support domain-specific settings.

## How domain separation works in Notifications {#domain-separation-notifications__section_ydt_kth_scb}

There are two basic components of domain separation and Notifications.  
* Notifications are process-separated (not data-separated).
* Notifications are triggered in two main ways:
  1. When a record is Inserted or UpdatedNotifications with matching conditions AND
     in the same domain and global domain as the inserted/updated record are
     processed.

  2. When an event defined in the notification is triggered
     1. Events typically have a target record. For example, \[incident.inserted\] event references the incident record being inserted.
     2. When an event is fired, notifications configured for that event in the same domain and global domain as the event's target record are processed.
     {#domain-separation-notifications__ol_rbz_3mb_qdb}
  {#domain-separation-notifications__ol_zcx_xlb_qdb}
{#domain-separation-notifications__ul_qbl_5lb_qdb}

Domains and email accounts

Domain separation is not supported in email accounts for these reasons:  
1. Sending mail: There is only one SMTP sender per account. This prohibits providing domains for each account, and they are not configurable.
2. 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.

{#domain-separation-notifications__ol_xkd_tmb_qdb} To learn more see [Inbound email actions](https://servicenow-prod.fluidtopics.net/FAehzMoI0~sKdpmQU~cjgA "Define an inbound email action to script how the system responds to an inbound email.").  
Note:  
If the number of email accounts exceeds 20, reception of email slows down.

## Use case {#domain-separation-notifications__section_usl_mgh_qdb}

If an instance is using the
[Domain separation plugin](https://www.servicenow.com/docs/access?context=c_DomainSeparationSetup&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US)
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](https://www.servicenow.com/docs/access?context=c_DelegatedAdministration&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US).
**Related concepts**   

* [Email templates](https://servicenow-prod.fluidtopics.net/iXLnNLgAAE9nyHDMEbRihw "Email templates enable administrators to create reusable content for the subject line and message body of email notifications.")
* [Email layouts](https://servicenow-prod.fluidtopics.net/x5fARNzjadceeKnQXiylrQ "Create reusable content for the message body of email templates.")
* [Email retention](https://servicenow-prod.fluidtopics.net/3xEJ4n8ulAVd4q4FGrIY0A "You can archive and eventually destroy email messages that you no longer need or if your Email table is excessively large.")
* [Watermarks on notification emails](https://servicenow-prod.fluidtopics.net/bHQBtKE5oqqm0bF97yvHOw "By default, a unique watermark label will be generated at the bottom of each notification email to allow matching incoming email to existing records.")
* [Email digests](https://servicenow-prod.fluidtopics.net/TeonCpDluhL1dVG~CpZSpQ "An email digest is a single email that summarizes the activity for a selected notification and its target record during a specified time interval. You can enable an email digest to reduce the number of notifications received when frequent updates to the associated record occur within a short time period.")
* [Email FAQs and troubleshooting notification emails](https://servicenow-prod.fluidtopics.net/SHxMvAzWvIY03fxq7AtH3g "Logs and diagnostics are provided to help determine whether notification emails are being sent and received successfully, what any issues are, and who receives the email.")  
**Related tasks**   

* [Create notification categories](https://servicenow-prod.fluidtopics.net/N2jGMUoz_N4G6Yg~OInZSg "You can create notification categories to identify and group related notifications that are listed in the notification settings for your users.")
* [Create an email notification](https://servicenow-prod.fluidtopics.net/1uxmFe3Zi5x_C3q5DOmU5Q "Create an email notification specifying when to send it, who receives it, what it contains, and if it can be delivered in an email digest.")
* [Parse an email thread](https://servicenow-prod.fluidtopics.net/_Ecer425ZkOHFbM4LlUd7w "When an email is received, parse the most recent message in an email thread by creating Email Reply Separators using specified string or regular expressions.")  
**Related topics**   

* [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=xanadu&pubname=xanadu-platform-security&ft:locale=en-US)

