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.
- Logical Data Separation Required?
- Scale?
- Platform requirements?
- Process differences?
- Administration requirements?
- Alternatives to Domain Separation include:
- Before Business Rules
- Access Controls
- Filters
- Security on related record
- Custom views
- Form layouts
- Notifications
- UI Action conditions
- Advanced reference qualifiers
Following KB article is very helpful for Understanding Domain Separation - Basics
https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0715934
