--- 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 --- # Domain separation levels of support # Domain separation levels of support {#ariaid-title1} * Freigeben Version: Australia * * Aktualisiert 12. März 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer Choose from three categories for domain separation of an application for your customers' organizations. Applications that support domain separation may support the separation of data and data routing only, have advanced business logic separation, or support tenant (customer) level administration of the application. These definitions delineate the support levels from the perspective of actual use cases and the people who implement them. ## Incremental ServiceNow support levels {#bp-domain-levels__section_x5w_kd2_rhb} {#bp-domain-levels__table_ucy_nd2_rhb__entry__3} | Level | Type | Summary | |:-|:-|:-| | No support | | * The domain field may exist on data tables, but no business logic exists to manage the data. * This level isn't considered domain-separated. {#bp-domain-levels__ul_jzy_h22_rhb} | | Basic | Customer data management | * Business logic: Ensures that data goes into the proper domain for the application's service provider use cases. * In the application, user interface, cache keys, reporting, rollups, aggregations, and so on, all consider the properties of the domain at run time. * Your instance owners must be able to set up the application to function normally across multiple tenants. {#bp-domain-levels__ul_gm3_222_rhb} Use case: When a service provider uses chat to respond to a customer's message, the client must be able to see the response. | | Standard | Customer process management | * Includes the Basic level * Business logic: Processes can be created or modified per customer by the service provider. The use cases reflect how the application is used by multiple service provider customers in a single instance. * Your instance owners must be able to configure minimum viable product (MVP) business logic and data parameters per customer for the specific application. {#bp-domain-levels__ul_smv_j22_rhb} Use case: Admin must be able to make comments required when a record closes for one customer, but not for another customer. | | Enhanced | Customer self-managed configuration | * Includes Basic and Standard levels * Enables service provider customers to modify business logic that is based on defined use cases. These configurations are UI-based and fail-safe so that configurations by one customer can't affect another customer. * The instance customers must be able to configure MVP business logic and data parameters themselves. {#bp-domain-levels__ul_bfg_422_rhb} Use case: Customer of a shared environment must be able to make changes according to impact, urgency, or priority within a domain. | | Effective domain\* | | In some cases, a platform feature or application may support service provider use cases even if the domain framework isn't being used. The use cases must be detailed to support domain separation. An asterisk (\*) after the support level indicates this kind of configuration. Use case: Before the New York release, Service Catalog had no domain support but the instance owners could configure separate catalogs and items for each tenant in a domain-separated instance by using user criteria. The result was that each tenant could use Service Catalog at a Standard level. | [ ] {#bp-domain-levels__table_ucy_nd2_rhb} To view all applications listed by their support level see [Application support for domain separation](https://servicenow-prod.fluidtopics.net/rk15B7vkwr79XNAcwC35uw "Many ServiceNow applications support domain separation in the base system but not all. Some supported applications include limitations on the data and administrative settings that can be domain-separated. These definitions delineate the domain separation support levels from the perspective of actual use cases and the people who use them."). ## Summary {#bp-domain-levels__section_scg_lt3_skb} Domain separation is a framework that you must use to make your applications aware of its customers. Consider the domain framework capabilities, your applications' business use cases, what the personas are, and how they use the application before you can use the framework to make your application supportable. **Zugehörige Konzepte** * [Domain separation explained](https://servicenow-prod.fluidtopics.net/x9xyVWl9u0yhkSMd6PgbBw "With domain separation, you can segregate application data, UI, and business logic, such as rules or workflows, in a single customer instance. Separating these elements into logically defined domains supports specific hierarchies for all customers using your applications.") * [Context and domain separation](https://servicenow-prod.fluidtopics.net/hSeeFgDzm2U__u_XsOCBsg "The context of a user's session determines the processes, data, and user interface (UI) as the user browses through list views, home pages, reports, and knowledge articles. The context is determined by the processes that you create, the business rules that you set, your workflows, and other factors.") * [How a database query works with domain separation](https://servicenow-prod.fluidtopics.net/yQ9RQVyEkZdMQEmVYhCGCw "Using database queries with domain separation in your customers' applications help them protect their data. These queries then speed up the configuration and build processes.") * [Domain-separate a custom table](https://servicenow-prod.fluidtopics.net/Lv2WmMnM3OxtInjuL8rlYw "You may need to create custom tables in separate domains. This topic covers both the procedure and the concept behind domain-separating a custom table.") * [Customizing domain properties and themes](https://servicenow-prod.fluidtopics.net/o~73HsH~C~Y8lCJBbqNjKA "You can customize your customers' company properties and themes within the domains that you have configured. Customization makes their instances fit in with their companies' overall look and feel.") * [Managing domain separation for specific uses](https://servicenow-prod.fluidtopics.net/~rh2XIdcd8JY~l2bgFgr~Q "You can set up separate domains for email notifications and customize the properties of catalog, tables, users, groups, and views. This enables you to provide more specific behavior in each domain, giving your customers more flexibility.") * [Configuring domain separation with the domain picker](https://servicenow-prod.fluidtopics.net/dB~D65eJSYPmKEJYOgd2RQ "Use the domain picker wisely, and remember the 80/15/5 approach so that you do not customize too much and impact the performance of your instance.") * [Domain separation performance considerations](https://servicenow-prod.fluidtopics.net/P8ZuAavQomgk_~ZYZYkfyw "As you configure domain separation in your application and services, make sure that you consider the number and properties of domains you create. Too many property-heavy domains can impact the performance of your instance.") * [Setting up domain hierarchies](https://servicenow-prod.fluidtopics.net/~BeGlrS5mkBAZC8MgNeHNw "You can avoid slowdowns and performance impacts in your instance by knowing how domain hierarchies work and by setting them up properly.") * [Checking domain logs for errors and warnings](https://servicenow-prod.fluidtopics.net/hTDpifH47t2Gr1s9ep3duA "Check the domain logs to find errors or warnings in your domain path processes and hierarchy configurations.") * [Importance of the Default domain](https://servicenow-prod.fluidtopics.net/s60j9ApH7YvVauD3Os2I4w "Organizing your domains is a crucial part of the domain separation process. If you don't set a default domain, new tasks and user records go to the global domain. Anyone can see the records in the global domain, which means that data can be seen when it is not supposed to.") * [Contains queries and domain access](https://servicenow-prod.fluidtopics.net/z9rKyulEpro~zy87l2cNMg "Use a \"contains\" query only in special cases, such as when users or groups need to see data from a domain that they don't have access to, but you don't want to move those users to a domain. Creating domain \"contains\" and user or group access for a domain should be an exception, only when absolutely needed.") * [Domain paths query method](https://servicenow-prod.fluidtopics.net/yWArrf6dWdJiSqzk7MV0rg "You can create effective queries with domain paths.") * [Slow queries and SQL debugging](https://servicenow-prod.fluidtopics.net/MDCvsO1Iv3cuVtEHAH_bfg "Debugging SQL and slow queries can help you resolve slowness issues in an instance.") * [Before Query business rules](https://servicenow-prod.fluidtopics.net/dYg_2l53Fdrn0m68dyF7wQ "You can use a Before Query business rule to help support data segregation on an instance. ServiceNow applications that support domain separation may support the separation of data and data routing only, have advanced business logic separation, or support tenant (customer) level administration of the application.") * [Avoiding domain path in scripts](https://servicenow-prod.fluidtopics.net/bv~55hFZ7r56GVb0sh0iDg "Domain paths can cause the values of your script to change or even break, so don't use them in scripts.") * [Domain separation and the Customer Service Management (CSM) plugin](https://servicenow-prod.fluidtopics.net/Vo~HSBl~YXh~9ao1ckJZHw "For the best outcome, be aware of how the properties in the CSM plugin work. When the plugin is enabled, you can see the status of your records in your domains.") **Zugehörige Verweise** * [Domain separation hierarchies](https://servicenow-prod.fluidtopics.net/SCHXcKE3qVwuIT~t3G1Hsg "Create a hierarchy when defining a domain architecture to track your processes and workflows.") * [Segregating and securing data with domain separation](https://servicenow-prod.fluidtopics.net/XOxpsOY5MXa0uH9QRefifQ "You can segregate and secure data on the ServiceNow platform in multiple ways, depending on your customer's needs. ") * [Alternatives to domain separation](https://servicenow-prod.fluidtopics.net/p_6ioFlafs3xFn~zvUKCyg "You can use a separate instance as an alternative to domain separation for your customers. A separate instance allows you the flexibility to meet the requirements for data separation within the groups and departments in an organization with little to no impact on others.") * [Evaluating the need for domain separation](https://servicenow-prod.fluidtopics.net/4r7B5rm_p0mj2kqvK6uXug "You may find that domain separation doesn't always work for your customers' organizations. It's best that you base your decision to go with domain separation by looking at your customers' needs.") * [Benefits of domain separation](https://servicenow-prod.fluidtopics.net/ILX1hP1qttb97unHeBSDJA "Domain separation may work better for your customers' organizations than any other method for separating the data between groups and departments.") * [Service provider reference architecture](https://servicenow-prod.fluidtopics.net/I7hvZlnhK2CMWNxs17Ur2w "Your customers can access service provider (SP) services by using a portal that is designed for them to reach their domain-separated instance.") * [Domain separation terms](https://servicenow-prod.fluidtopics.net/H1gx~UAruHKGV3488YLtEg "With a ServiceNow instance, you can improve efficiency, add greater security, and increase performance for your customer organizations. It's helpful to understand some of the most common terms as you create your configurations.") * [Domain assignments](https://servicenow-prod.fluidtopics.net/mcw9B6D7asbF5cb6Qw3jhg "How you assign a domain impacts the value of the sys_domain field. The assignments contain designs and business properties that affect how the application functions in each domain.")