---
sourceDocument: Brazil IT Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/it-service-management

 Release :

    - brazil

ft:locale :

    - en-US

ft:publication_title :

    - Brazil IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Domain separation

# Domain separation and Coaching {#ariaid-title1}

Release version: Brazil  
Updated September 10, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read
Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Domain separation and Coaching

Domain separation in Coaching allows ServiceNow customers to logically separate data, processes, and administrative tasks into distinct domains.
This separation controls user access and visibility, enabling multi-tenant use cases where data and functionality are isolated by domain.
Coaching supports domain separation at runtime with no additional setup required, making it straightforward for organizations to manage coaching data and activities across different domains.
Show full answer Show less  

## Key Features

* **Support for multiple coaching tables:** Domain separation is enabled for key Coaching tables such as Coaching Opportunity, Coaching Assessment, Virtual Coach, and Trainings.
* **Data visibility control:** Coaches and trainees can only access coaching assessments, trainings, and opportunities within their assigned domain.
* **Domain metadata:** Records include Domain and Domain Path fields to identify the domain context, which can be added to personalized lists for easier management.
* **Inheritance and multi-domain access:** Coaching opportunities created at a parent domain level are visible in all child domains, while users must belong to the domain of integrated applications to associate assigned training.
* **Runtime support across UI and reporting:** Domain separation applies to user interface, cache keys, reporting, rollups, and aggregations, ensuring consistent domain isolation.

## Practical Use Cases

* A Coaching admin managing multiple domains can create or update coaching opportunities and assessments in specific domains, ensuring content is domain-appropriate.
* Service providers using chat to respond to tenant customers can ensure responses are visible only within the appropriate domain.
* Trainees can access coaching assessments within their domain or parent domains, maintaining proper data segregation while allowing necessary visibility.
* Integration with other applications respects domain boundaries, requiring user domain membership to associate training records.

## Key Outcomes

ServiceNow customers leveraging domain separation in Coaching gain precise control over data access and visibility across multiple tenants or organizational units. This capability supports secure multi-tenant environments, ensures compliance with data governance policies, and improves management of coaching activities by domain. The built-in support without extra configuration reduces complexity while maintaining robust domain isolation.  
Domain separation is supported in Coaching. 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: Basic {#cf-domain-separation-coaching__section_nyz_myq_xkb}

{#cf-domain-separation-coaching__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.
{#cf-domain-separation-coaching__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.{#cf-domain-separation-coaching__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=brazil&pubname=brazil-platform-security&ft:locale=en-US).{#cf-domain-separation-coaching__p_msc_nfg_h1c}

## Domain Separation Overview {#cf-domain-separation-coaching__section_pvf_wkx_vcb}

All tables including Coaching Opportunity, Coaching Assessment, Virtual Coach, and
Trainings support domain separation so the
coach and Coaching admin can view records within the (tenant) domain to which they belong.

## How domain separation works in Coaching {#cf-domain-separation-coaching__section_icv_pkb_jfb}

Domain separation is supported in Coaching with no setup or configuration required. You can create coaching opportunities and coaching assessments in separate domains, including the global domain.

Coaching assessments extend the platform Task \[task\] table.

When domain separation is implemented, coach and trainee users can view coaching assessments and
trainings only in the domain assigned. The
Domain and Domain Path columns are available for coaching opportunities, coaching assessments, virtual coaching, and
trainings 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.  
Note:  
If the domain column is not shown, select the Update Personalized List icon and add the required column. You can also add the domain path column, if desired.

## Domain-separated tables {#cf-domain-separation-coaching__section_jpz_skb_jfb}

* Coaching Assessment \[sn_coaching_assessment\]
* Coaching Opportunity \[sn_coaching_opportunity\]
* Trainings \[sn_coaching_recommendation\]
* Assigned Training \[sn_coaching_assessment_recommended_learning\]
* Assigned Training \[sn_coaching_opportunity_recommended_learning\]
* Virtual Coach \[sn_coaching_opportunity_virtual_coach_m2m\]
* Virtual Coaching \[sn_coaching_virtual_coach\]
{#cf-domain-separation-coaching__ul_tnv_k2g_pfb}

## Use cases {#cf-domain-separation-coaching__section_u1m_2lb_jfb}

* A Coaching admin that belongs to a parent domain creates a coaching opportunity at a parent domain level or at a child domain level. Coaching opportunities created at a parent level are available to view in all domains.
* A Coaching admin has access to multiple domains but wants to update content in a record within a specific domain. The domain specified in the record drives the functionality of that record and reference fields.
* A Coaching user that belongs to the Acme domain can view the coaching assessment task created in the Acme domain.
* A Coaching user wants to associate an assigned training for an integrated application in the Acme domain. The user must belong to the domain of the integrated application from which a record is associated.
* The trainee user of a parent domain can view a coaching assessment of the parent as well as of all child domains of that parent. A trainee user must belong to the Acme domain, its parent domain, or the global domain to view that coaching assessment.
{#cf-domain-separation-coaching__ul_pjx_3kk_4fb}
**Related topics**   

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