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

# Domain separation and Skills 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 in the Skills Management app, and configured to apply to
all features of the application. Separation of data is configured along with separation of logic
and process.

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

## Support level: Basic {#domain-separation-skill-management__section_j4f_wyv_5mb}

{#domain-separation-skill-management__domain-sep-supported}  
* Business logic: Ensure that data goes into the proper domain for the application's service provider use cases.
* The application supports domain separation at run time. The domain separation includes separation from the user interface, cache keys, reporting, rollups, and aggregations.
* The owner of the instance must set up the application to function across multiple tenants.
{#domain-separation-skill-management__ul_yhr_g2j_xkb}

Sample use case: When a service provider (SP) uses chat to respond to a tenant-customer's
message, the customer must be able to see the SP's response.{#domain-separation-skill-management__p_lsc_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-skill-management__p_msc_nfg_h1c}

## How domain separation works in Skills Management {#domain-separation-skill-management__section_yzb_s54_zgb}

Domain separation is supported in Skill Management with no explicit setup or configuration
requirements. Skills, skill categories, skills levels can be created in separate domains,
including the global domain. When domain separation is implemented, people with skill app
roles can view skill information only in the domain assigned. Domain and
Domain Path columns are available for all Skill tables provided with the
base system. The Domain column contains the name of the domain to which
the event or alert belongs, and the Domain Path column contains the
unique domain identifier.
{#domain-separation-skill-management__table_jt3_3x4_zgb__entry__2}

| Table name | Description |
|-|-|
| sys_user_has_skill | User skill information |
| cmn_skill | Main skill table |
| cmn_skill_category | Define skill categories |
| cmn_skill_level_type | Define skill level type |
| cmn_skill_level | Define skill level |
| sys_group_has_skill | Group skills |
| cmn_skill_contains | Define skills contained within skills |
| task_m2m_skill | Task skill information |
[ ]

{#domain-separation-skill-management__table_jt3_3x4_zgb}  
Hinweis:  
If the domain column is not shown, click the Update Personalized List icon and add the required column. You can also add the domain path column, if desired.  
Use cases:

* A Skill Manager that belongs to the Acme domain creates a skill and wants to view and associate it to user in the Acme domain. A user must belong to the Acme domain, its parent domain, or the global domain to view the skill record.
* A Skill Manager that belongs to a parent domain tries to view a skill in a child domain. The user of a parent domain can view a skill record of the parent as well as all child domains of that parent.
* A Skill Manager that belongs to a parent domain wants to create/associate a skill on behalf of another user in the Acme domain. A user must belong to the same domain as the user for which the skill record is created.
* A Skill Manager wants to associate a record for an integrated application in the Acme domain. A user must belong to the domain of the integrated application from which a record is associated.
* A Skill Manager has access to multiple domains but wants to update a record with content within a specific domain. The domain specified for the current record drives the functionality of that record and reference fields.
{#domain-separation-skill-management__ul_dsf_4y4_zgb}