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


---

# Visibility domains and Contains domains

# Visibility domains and Contains domains {#ariaid-title1}

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

Visibility domains control what a specific user or group of users can see. "Contains"
domains control what an entire domain of users can see.

## Visibility domains {#c_DomainVisibility__section_sb3_hk4_2cb}

The "Visibility domains" element determines whether users from one domain can access records
from another domain. Associate this element with User \[sys_user\] and Group \[sys_user_group\]
records in related lists on those records. Groups grant their members the visibility domains of
the group. When a user leaves a group, they lose the group's visibility domains. Granting users
a visibility domain grants all the rights to the records in that domain based on ACL (access
control list) rules.

A visibility domain:  
* Is a user-to-domain relationship and is explicitly granted.
* Is not a child domain.
* Is not controlled by the selection in the domain picker. Users with access to a visibility domain always see data in that domain and its child domains.
{#c_DomainVisibility__ul_ppq_c44_4s}  
Hinweis:  
Using visibility domains excessively is not recommended. Although visibility is one method to allow users to access records, it's best to use contains domains for more robust control.

## Contains domains {#c_DomainVisibility__section_lxd_pk4_2cb}

Normally parent-child relationships define the domain hierarchy. A contains domain lets you
relate domains on an as-needed basis, independent of parent-child relationships. However,
contains domains grant visibility only to domain data. Processes remain unaffected by contains
relationships.

A contains domain:  
* Is a many-to-many, domain-to-domain relationship.
* May have child domains. When a domain is selected, you can see the data from that domain and its children.
* Is controlled by the selection in the domain picker.
{#c_DomainVisibility__ul_pr5_yj4_2cb}  
Hinweis:  
When you open the domain record, the scope is set to that record's domain, so you can see only child domains. Choose Toggle Domain Scope from the menu to populate the related list.

## Contains domain example {#c_DomainVisibility__section_nqz_jt2_ybb}

When a user's home domain is A, and the A domain contains domains B and C, they all become
peer domains. That means the user sees data from domains A, B, and C while in their home domain
A. If users change domains with the domain picker to Domain B, they see only data in Domain B.
When users interact with a record from Domain B or Domain C directly, they see only data for
that domain.

## Visibility domain example {#c_DomainVisibility__section_xnr_kj2_ybb}

Using domain visibility, if Don Goodliffe is in the Database domain, and Bow Ruggeri is in the
Network domain, and no incidents are in the global domain, then Don cannot access Bow's
incidents because of data separation.

## Inheriting visibility domains based on group membership {#c_DomainVisibility__section_mbt_vl2_ybb}

If you set the domain table to the Group \[sys_user_group\] table, users can inherit visibility
domains based on their group membership.
**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.")
* [Domain assignment](https://servicenow-prod.fluidtopics.net/p8nHbzEnZXZJ~XFrPVR_Mg "By default, domain separation adds a domain field to tables and their extensions.")
* [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.")
* [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.")  
**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.")
* [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.")