logo

NJP

ServiceNow Domain Separation

New article articles in ServiceNow Community ยท Jul 04, 2025 ยท article

Crack the Secret of Superpowers in ServiceNow Domain Separation: Accelerating Performance of your Organization ๐Ÿ”โœจ

ServiceNow Domain Separation isn't just a regular feature; it's like handing over a magic wand to modern businesses. With Domain Separation, companies can play hide and seek with data, processes, and user access by creating secret hiding places within one instance. It's akin to transforming your office into Hogwarts ๐Ÿฐ, where confidential information is as concealed as the Chamber of Secrets and workflows glide smoother than a Quidditch match. โœจ๐Ÿš€

  • What is Domain Separation?
    • The ServiceNow Sub-Tenant Platform Architecture, also known as Domain
      Separation, allows application data, processes, and administrative tasks to
      be separated into logical groupings called domains.
  • When to use Domain Separation?
    • Need to enforce absolute data segregation between business entities (data separation) but
      require centralized management of ServiceNow.
    • Customize business process definitions and user interfaces for each domain (delegated
      administration).
    • Maintain global processes and global reporting in a single instance.
    • Have minor or moderate process differences between business entities.
  • Managed Service Providers (MSPs)
    • The MSP manages the instance and the environment for its
      customers, and each customer's data is separated into its
      domain so one customer's data is not visible to another
      customer.

NOTE: Before activating Domain Separation, consult with ServiceNow to verify that it is suitable for

your environment. Domain separation adds a level of administration overhead. Although it can be

disabled, it cannot be removed from an instance.

  • Benefits of Domain Separation
Providers Tenants
Volume licensing Lower minimum license threshold
Centralized administration of customers as tenants Pre-built processes and capabilities
Data segregation Reduced staff requirements
Global reporting Faster on-boarding
Upgradability and scalability Shared instance costs
Services offered by the provider
  • When to use Domain Separation?

If the answer to any of these questions is no, a single instance should be used

instead of Domain Separation.

  1. Logical Data Separation Required?
  2. Scale?
  3. Platform requirements?
  4. Process differences?
  5. Administration requirements?
  6. Alternatives to Domain Separation include:
  7. Before Business Rules
  8. Access Controls
  9. Filters
  10. Security on related record
  11. Custom views
  12. Form layouts
  13. Notifications
  14. UI Action conditions
  15. Advanced reference qualifiers

Following KB article is very helpful for Understanding Domain Separation - Basics

https://support.servicenow.com/kb?id=kb%5Farticle%5Fview&sysparm%5Farticle=KB0715934

View original source

https://www.servicenow.com/community/developer-articles/servicenow-domain-separation/ta-p/3310031