domain-separation

Domain separation in ServiceNow partitions data and processes between distinct domains to enable multi-tenancy. You create a domain for each customer, assign administrators, and enable domain separation settings to enforce tenant data isolation and prevent scope creep.

Domain separation is a ServiceNow architecture that partitions data and processes between domains to enforce tenant isolation. You need it when managing multiple customers or tenants in a single environment and must prevent data leakage across tenant boundaries.

Domain-aware GlideRecord queries respect domain separation by returning only records visible to the user's current domain. You configure domain picker behaviors and user domain memberships to control cross-domain access and ensure query results match tenant boundaries.

Domain separation supports Managed Service Provider workflows by providing domain-aware visibility and control to administrators. MSPs can partition data and configuration by domain, enabling secure onboarding of new customers with domain-specific rules and isolated tenant data.

To onboard a new customer using domain separation, create a new domain for the customer, assign an admin to that domain, and enable basic domain separation settings. This enforces tenant isolation and allows configuration of domain-specific rules for the new tenant.

Cross-domain queries in ServiceNow return unexpected records when domain picker behaviors or user domain memberships are misconfigured. Domain separation enforces data isolation, so reviewing domain-aware query patterns and cross-domain access settings ensures records respect tenant boundaries.