---
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 plugin

# Domain separation plugin {#ariaid-title1}

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

The Domain Support - Domain Extensions Installer plugin activates several domain
separation features and properties at once. This plugin is typically referred to as the Domain
Separation plugin.

## Recommended practice for activating the Domain Separation plugin {#domain-sep-plugin__section_tp4_qh3_blb}

As part of domain separation development, administrators must [request activation](https://servicenow-prod.fluidtopics.net/qb1zon1C6n_KKQdU1g~1QA "All domain support features are activated with a plugin called Domain Support - Domain Extensions Installer. Administrators can request activation of this plugin.") of this plugin. For
best results, activate the Domain Separation plugin at the start of the development process,
preferably before any other plugin is enabled.  
Wichtig:  
Request to activate the Domain Extensions Installer plugin (com.glide.domain.msp_extensions.installer) before activating Domain Separation (plugin com.snc.pa.domain_support).

If you enable Domain Separation towards the end of ServiceNow
implementation or once an instance has gone live, your application is at risk in both
performance and process. On established instances, depending on how things were structured
in development, the risk to the platform and its usability could be high. To learn more
about domain separation process, see [Exploring domain separation](https://servicenow-prod.fluidtopics.net/PI2FTsbWjIyGcBInkfq86w "With domain separation you can separate data, processes, and administrative tasks into logically defined domains.").

For instance, when the Domain Separation plugin is enabled, the Domain
(sys_domain) column is added to the task table and every existing record is automatically
placed in global. To use a script to assign all of the records into
the correct domains, an established parent/child hierarchy is required. These types of
scripted actions risk data corruption or loss, and possible production down time as large
amounts of data are moved. Much of the platform code also is placed into
global, such as business rules, client scripts, form views, and
workflows.

If
a customer creates code or modifies ServiceNow code, there is risk to
platform performance and usability.

Instance owners could severely delay their implementation or experience lengthy down-times
with this type of approach.

## Features of the Domain Separation plugin {#domain-sep-plugin__section_fqk_w2c_nmb}

These features are enabled when you activate the plugin:

* Domain separation is based on the Domain `[sys_domain]` table.
* Delegated administration lets each domain have separate policy.
* All records are part of the global domain.
* The current user's domain determines the domain to use when viewing or operating on a record in a different domain.
{#domain-sep-plugin__ul_csm_s2c_nmb}
**Zugehörige Verweise**   

* [Domain separation recommended practices for service providers](https://servicenow-prod.fluidtopics.net/PFPBfqQYeA_4Q9vVvFyyvw "You can create, implement, and maintain domain separation for your applications and services.")