---
sourceDocument: Australia Platform security
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/platform-security

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia Platform security

ft:clusterId :

    - psec

bundleId :

    - psec

workflow :

    - Platform


---

# Definition of domain separation

# Definition of domain separation {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

With domain separation (also known as the ServiceNow® Multitenant
Platform Architecture), you can segregate application data, UI, and business logic in a single
customer instance that supports hierarchical modeling with cross-tenant (customer)
intelligence.

## Properties of domain separation {#bp-dom-sep-definition__section_hpq_2kt_phb}

Domain-separated ServiceNow applications are defined with the
following properties:  

Data separation
:   Enables customers to see only the data that they have permissions to see. Customers
    can be granted access to other customer data but cannot query customer data if they
    don't have access.

UI separation
:   Supports a customer-specific experience for UI elements such as views, lists,
    labels, and so on.

Business logic separation
:   Supports customer-specific system policies such as email notifications, business
    rules, client scripts, UI policy, and UI actions.

Hierarchical modeling
:   Supports nested-multitenancy so parent tenants (customers) can access child customer
    resources. The business logic for parent customers runs automatically for child
    customers and can be overridden at any level.

Cross-customer intelligence (domain scope)
:   Handles automatically the data, metadata, business logic, and processing context for
    tenants that have access to additional tenant data.