Thank you for your feedback.
Form temporarily unavailable. Please try again or contact to submit your comments.

Domain separation and skills management

Log in to subscribe to topics and get notified when content changes.

Domain separation and skills management

Domain separation in Skill Management app is 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 1

Domain separation is supported in this application. Not all ServiceNow applications support domain separation; some include limitations on the data and administrative settings that can be domain separated. To learn more, see Application support for domain separation. The Skills Management application enables you to track and organize skill data of service agents and employees in a domain separated environment. The skill data can be used for skill-based task assignment, skill gap analysis to identify coaching and training needs, career growth planning, workforce optimization and skill-based hiring. All skill related tables support domain separation so that the people with skill user, skill manager and skill admin roles can view only the skill and related tasks within the (tenant) domain to which they belong.

How domain separation works in Skills Management

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.

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
Note: 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.