---
sourceDocument: Yokohama Enable AI
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/intelligent-experiences

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Enable AI

ft:clusterId :

    - platai

bundleId :

    - platai

workflow :

    - Platform


---

# AI Skill Kit roles

# AI Skill Kit roles {#ariaid-title1}

Release version: Yokohama  
Updated July 15, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read  
Certain roles are required to use AI Skill Kit functionality.

## How roles work in AI Skill Kit {#na-skill-kit-roles__section_c5n_qbm_vjc}

Three separate role concepts apply when you build and deploy a custom skill. Understanding the difference helps you plan access before you start and troubleshoot permission errors after you deploy.

Roles required to use the AI Skill Kit
:   There are some roles that users need to perform an activities in AI Skill Kit, such as installing the plugin, building a skill, or activating a published skill. These roles are assigned to the people on your team who build and manage skills. For a list of the roles required
    for each activity, see the [Roles required for common tasks](https://servicenow-prod.fluidtopics.net/1Jf73n0gaXJe8XsAv0vZ_w#section_roles_by_task) table.

Roles required to trigger skills
:   These are roles a user must have to trigger a published skill on your instance. These roles are configured within the skill configuration as part of its access control list (ACL). The ACLs are separate from the roles required
    to build the skill. To learn more, see .

Roles that a skill runs under
:   The roles that a skill operates with while it runs, which control what data and actions the skill can access on behalf of the triggering user. These are configured on the skill as role restrictions. Role restrictions are also
    separate from the roles required to build the skill. To learn more, see .

Two roles ship with AI Skill Kit:

* sn_skill_builder.admin for building, editing, and publishing skills.
* sn_skill_builder.model_admin for managing the LLMs available to skills.

{#na-skill-kit-roles__ul_u2y_rbm_vjc}

The platform admin role is also required at two points: to install AI Skill Kit and to activate a published skill in AI Admin Hub. In many deployments, one person holds all three roles.  
Note:  
The ACL and role restriction concepts apply to the skill's runtime users, not to the people building the skill. If you're planning access for your build team, you only need the roles listed in the [Roles required for common tasks](https://servicenow-prod.fluidtopics.net/1Jf73n0gaXJe8XsAv0vZ_w#section_roles_by_task) table.

## Roles required for common tasks in AI Skill Kit {#na-skill-kit-roles__section_roles_by_task}

Most work in AI Skill Kit requires the sn_skill_builder.admin role, including creating, cloning, editing, configuring, testing, evaluating, and publishing skills, and calling skills from scripts.

Two activities require the platform admin role instead: installing AI Skill Kit and activating a published skill in AI Admin Hub.

Triggering an activated skill from the UI requires whatever roles are configured in the skill's ACL. To learn more, see .

## Skill kit admin (sn_skill_builder.admin) {#ariaid-title2}

This user can create, update, and publish skills in AI Skill Kit. This role is mandatory to use AI Skill Kit.

### Contains Roles {#skill-builder-admin-role__section-feature-role-contains-roles}

List of roles contained within the role.

None.

### Groups {#skill-builder-admin-role__section-feature-role-groups}

List of groups this role is assigned to by default.

None.

### Special considerations {#skill-builder-admin-role__section-feature-role-considerations}

None.