Domain separation and Coaching

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
    • Summarize
    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 enables ServiceNow customers to logically segregate data, processes, and administrative tasks into distinct domains. This separation controls user access to data and ensures that coaching activities such as opportunities, assessments, virtual coaching, and trainings are confined to their respective domains. Domain separation is supported out-of-the-box in Coaching with no additional setup required, allowing multiple tenants or business units to operate securely and independently within the same instance.

    Show full answer Show less

    Key Features

    • Support for multiple coaching tables: Domain separation applies to key Coaching tables, including Coaching Opportunity, Coaching Assessment, Virtual Coach, and Trainings.
    • Data visibility and access control: Coaches and trainees can only view coaching assessments and trainings within their assigned domain, ensuring privacy and security.
    • Domain columns: Records include Domain and Domain Path fields to identify the domain ownership of coaching records, which can be added to list views for better visibility.
    • Parent and child domain hierarchy: Coaching admins in parent domains can create opportunities accessible across child domains, supporting multi-level organizational structures.
    • Integration with platform tasks: Coaching assessments extend the platform Task table and respect domain boundaries during creation and access.
    • Run-time enforcement: Domain separation is enforced at run time, affecting the user interface, caching, reporting, rollups, and aggregations.

    Practical Use Cases for ServiceNow Customers

    • A service provider can manage coaching opportunities and assessments across multiple tenants while ensuring tenant data is isolated and secure.
    • Coaching admins with multi-domain access can update content specific to a domain without impacting others.
    • Coaches and trainees only see coaching records relevant to their domain, preventing unauthorized access.
    • Trainees in a parent domain can view coaching assessments from both the parent and all child domains, supporting hierarchical visibility requirements.
    • For integrated applications requiring domain-specific assigned training, users must belong to the same domain as the integrated application for proper record association.

    What Customers Can Expect

    Implementing domain separation in Coaching empowers organizations to manage multiple tenants or divisions securely within one ServiceNow instance. It ensures data integrity and privacy across coaching activities without additional configuration. Customers benefit from streamlined administration of coaching processes with clear domain-based access controls, enabling scalable and compliant coaching operations aligned with their organizational structure.

    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

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

    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.

    For more information on support levels, see Application support for domain separation.

    Domain Separation Overview

    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

    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

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

    Use cases

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