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

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Domain separation and Document Management

# Domain separation and Document Management {#ariaid-title1}

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

Domain separation is supported for Document Management. Domain separation enables you to separate data, processes, and administrative tasks into logical groupings called domains. You can control several aspects of this separation, including which users can see and access data.

## Support level: Standard {#domain-separation-document-services__section_v1l_n5r_xkb}

* Includes all aspects of Basic level support.
* Application properties are domain-aware as needed.
* Business logic: The service provider (SP) creates or modifies processes per customer. The use cases reflect proper use of the application by multiple SP customers in a single instance.
* The instance owner must configure the minimum viable product (MVP) business logic and data parameters per tenant as expected for the specific application.
{#domain-separation-document-services__ul_tfh_drj_xkb}

Sample use case: An admin must be able to make comments required when a record closes for
one tenant, but not for another.{#domain-separation-document-services__p_ssc_nfg_h1c}

For more information on support levels, see [Application support for domain
separation](https://www.servicenow.com/docs/access?context=domain-separated-apps&version=australia&pubname=australia-platform-security&ft:locale=en-US).{#domain-separation-document-services__p_tsc_nfg_h1c}

## Overview {#domain-separation-document-services__section_wnh_ggm_qtb}

Document Management provides an access level approach to controlling the
document access and providing security to the users.

## How domain separation works in Document Management {#domain-separation-document-services__section_ujj_hhm_qtb}

When domains are separated in Document Management, users can see and manage
documents and give access privileges only in their own (tenant) domain.

A user in the parent domain has access to documents in the child domain.

When a user creates a document, document list or document entries, then their domain is the
same as the user's domain.

When the owner of the document changes then the related versions,
references,
and permission record's domain is updated with the domain of the parent document.

## Use cases {#domain-separation-document-services__section_inl_h2t_qtb}

* Documents

  Documents can be edited or accessed only within their
  domain. Access to a document can become void if a user belongs to a different domain
  from the document's domain.
  * Users in the global domain can access documents in all domains when the read access is granted to the user.
  * Users in a non-global domain can access documents only in the same domain and global domain when document access is granted to the user.
  {#domain-separation-document-services__ul_upf_m2t_qtb}
* Versions, References and Permissions table
  * Users can access the versions, references, and, permissions table records only if they have access to the parent document.
  * If a user has access to the target record in the references table, access to the parent document is granted only if inherited access is enabled for the document and the user is in the same domain as the parent document.
  {#domain-separation-document-services__ul_akw_q2t_qtb}
* List and List Entries

  List and List Entries have domain
  pointing to the current user domain and can be accessed by the users with document admin
  rights.
{#domain-separation-document-services__ul_kjc_f2t_qtb}

## Known issues {#domain-separation-document-services__section_lkg_fft_qtb}

If a document contains references and if the owner of the document is changed and does not
have access to the target record of one of the references, then the reference record might
not be visible to the new owner.

For example, if the document owner, User A (Domain: D1) is changed to User B (Domain: D2)
and User B does not have access to the target record of the reference
table,
User B might not be able to see the reference record.
**Zugehörige Verweise**   

* [Components installed with Document Management](https://servicenow-prod.fluidtopics.net/5uSIVAMBIaD2_TJfV~xD6g "Several types of components are installed with activation of the Document Management plugin, including tables and user roles.")
* [Document Management roles](https://servicenow-prod.fluidtopics.net/OyK~~b4dXTMxTuPK~jN0xA#document-management-roles "Document Management is installed with these roles.")
* [Granular admin roles in Document Management](https://servicenow-prod.fluidtopics.net/72eKKWQRsf3s~mAvONsIOQ "Granular admin roles enable organizations to assign specific administrative permissions based on functional responsibilities, replacing broad admin access with targeted role assignments. Use the new admin roles to grant users administrative capability without using the admin role.")  
**Zugehörige Informationen**   

* [Domain separation for service providers](https://www.servicenow.com/docs/access?context=domain-sep-landing-page&version=australia&pubname=australia-platform-security&ft:locale=en-US)