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

# Domain assignment {#ariaid-title1}

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

By default, domain separation adds a domain field to tables and their
extensions.

You can also extend domain separation to any new tables you create by adding a
sys_domain field to the table's dictionary definition. By default, the
system only domain-separates platform and baseline application tables where appropriate.  
Warnung:  
ServiceNow does not recommend domain-separating platform tables (any table with the sys_ prefix such as the Dictionary Entry \[sys_dictionary\] and Dictionary Entry Override \[sys_dictionary_override\] tables) because it can produce unexpected results.

Each record is assigned a single domain. That domain is stored in the sys_domain field. Several tables, by default, have the sys_domain column
and are already domain separated.  
The value of the sys_domain field contains the domain assigned to the record by any of the following:

* Company to which the user belongs
* Business rule when creating record
* Module used when creating record
* Form template used when creating record
* Domain of the parent record
* Domain assigned to User record
* Domain of the user who creates it
{#c_DomainAssignment__ul_yhy_r2h_1r}

The system prevents the following tables from being domain separated:

* Access Control `[sys_security_acl]`
* Script Include `[sys_script_include]`
* System Property `[sys_properties]`
* Security Exclusion/Inclusion List Entities `[sys_security_restricted_list]`
* Dictionary Entry `[sys_dictionary]`
* Dictionary Entry Override `[sys_dictionary_override]`

{#c_DomainAssignment__ul_srr_v2h_1r}

## Assigning users to companies

Administrators can quickly assign users to a domain by assigning them to a company. After
users are assigned to a domain, records automatically inherit the user's domain.

For example, assigning Bow Ruggeri to the ACME company automatically assigns him to the ACME
domain. Assigning Don Goodliffe to the Initech company automatically assigns him to the Initech
domain. Any records they create are automatically added to the appropriate domain.

## Using business rules to assign domains

Administrators can use a business rule to automatically set a domain value when creating a
record. The business rule must set a value in the sys_domain field.
Administrators must ensure there is a sys_domain column available for the
record's table. To learn more see [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.").

## Using modules to assign domains

Administrators can use the sysparm_domain URL parameter to
automatically assign new records to a particular domain from a module. Administrators must
create a module with an Argument value of: `sysparm_domain=sys_ID
of domain`.

## Using form templates to assign domains

Administrators can use a form template to automatically assign new records to a particular
domain. Administrators must add the sys_domain field to the form and
select a domain value. For example, setting the sys_domain field to
TOP/ACME domain automatically assigns all records from this template to
the TOP/ACME domain.

## Domain inheritance on tables

By default, related records inherit the domain of the parent record. For example:

* A change task record inherits the domain of the parent change request record.
* A problem record inherits the domain of the parent incident record.
{#c_DomainAssignment__ul_s52_jfh_1r}

## Automatic domain assignment based on user domains

If no other domain conditions apply, a record automatically inherits the domain of the user
who creates it.
**Zugehörige Konzepte**   

* [Configuration that can be delegated to internal or external customers](https://servicenow-prod.fluidtopics.net/pOd6TVzcEYSOtU6NbkzLxw "Domain separation is designed to give ServiceNow service providers (SPs) the ability to configure the services they offer to their customers. It is not designed to enable their customers to administer those services themselves, except in a few areas that this topic details.")
* [Visibility domains and Contains domains](https://servicenow-prod.fluidtopics.net/5abdd86~QaxlGJI_IFH7TA "Visibility domains control what a specific user or group of users can see. \"Contains\" domains control what an entire domain of users can see.")
* [Domain scope](https://servicenow-prod.fluidtopics.net/K6SrKpNf2jlk8mqnnYF8Ag "Domain scope defines what users can and cannot access.")
* [Concepts for service providers](https://servicenow-prod.fluidtopics.net/_QM8GOzYXmovbRj65yC7hQ "These concepts work with the existing ServiceNow platform capabilities to help you solve for common use cases.")  
**Zugehörige Verweise**   

* [Installed with domain separation](https://servicenow-prod.fluidtopics.net/36~JdKE54_AB1YemUw0W_w "Several platform components are added or modified with domain separation.")