Domain separation and Coaching
Summarize
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 of data based on domain membership, ensuring that data is properly segmented for multi-tenant or service provider use cases. Coaching supports domain separation natively with no additional setup required, enabling coaches and administrators to view and manage records only within their assigned domains.
Show less
Key Features
- Full Domain Separation Support: Includes Coaching Opportunity, Coaching Assessment, Virtual Coach, and Trainings tables, all respecting domain boundaries.
- Runtime Enforcement: Domain separation works at runtime affecting the user interface, cache keys, reporting, rollups, and aggregations.
- Multi-Domain Access: Coaching admins can create coaching opportunities at parent or child domain levels. Opportunities created at the parent domain are visible across all child domains.
- Domain-Specific Views: Coaches and trainees see only domain-assigned coaching assessments, trainings, and virtual coaching records.
- Domain Columns: Records include Domain and Domain Path fields to identify and filter data by domain.
- Integration Considerations: Users must belong to the domain of any integrated applications when associating assigned training records.
Practical Use Cases
- A service provider responding to tenant customers via chat can ensure that tenant users see responses relevant to their domain.
- A Coaching admin managing multiple domains can update content specifically in one domain without affecting others.
- Users in a child domain can access coaching assessments and trainings relevant to their domain, while parent domain users can access data across child domains.
What Customers Can Expect
ServiceNow customers implementing Coaching with domain separation will experience controlled, secure data segregation aligned with their organizational or tenant structures. This ensures that coaching activities, assessments, and training assignments are visible and accessible only to authorized users within their domains, enhancing data privacy and governance while supporting multi-tenant operations seamlessly.
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.
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.