--- sourceDocument: Australia Enable AI sourceDocumentLink: https://www.servicenow.com/docs/r/intelligent-experiences Release : - australia ft:locale : - en-US ft:publication_title : - Australia Enable AI ft:clusterId : - platai bundleId : - platai workflow : - Platform --- # AI Skill Kit roles # AI Skill Kit roles {#ariaid-title1} Release version: Australia Updated July 15, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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://www.servicenow.com/docs/q1jyvceh_2MhFoq6r6VBdQ#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 [Configure security controls for a skill](https://www.servicenow.com/docs/waDEzQpkNzung8fyrs~aPA "You must define an access control list (ACL) and role restrictions for all skills. An ACL enables you to restrict who is able to access and execute a skill to only users with the correct role. Role restrictions enable users to limit roles during skill execution."). 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 [Configure security controls for a skill](https://www.servicenow.com/docs/waDEzQpkNzung8fyrs~aPA "You must define an access control list (ACL) and role restrictions for all skills. An ACL enables you to restrict who is able to access and execute a skill to only users with the correct role. Role restrictions enable users to limit roles during skill execution."). 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://www.servicenow.com/docs/q1jyvceh_2MhFoq6r6VBdQ#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 [Configure security controls for a skill](https://www.servicenow.com/docs/waDEzQpkNzung8fyrs~aPA "You must define an access control list (ACL) and role restrictions for all skills. An ACL enables you to restrict who is able to access and execute a skill to only users with the correct role. Role restrictions enable users to limit roles during skill execution."). ## Skill Kit admin (sn_skill_builder.admin) {#ariaid-title2} Create, configure, test, and publish skills in AI Skill Kit. Assign this role to anyone developing skills on your instance. ### Contains roles {#skill-builder-admin-role__section-feature-role-contains-roles} None. ### Groups {#skill-builder-admin-role__section-feature-role-groups} None. This role is not assigned to any groups by default. ### Tasks requiring this role {#skill-builder-admin-role__section-feature-role-tasks} The sn_skill_builder.admin role is required for the following tasks: * [Create a skill](https://www.servicenow.com/docs/LKwxb28v59W_28ULmgLTkg "Create a custom skill for Otto. Creating a custom skill enables you to have greater flexibility with Otto's generative AI capabilities.") * [Clone a skill](https://www.servicenow.com/docs/~X_EnP2VBPQTxsfgEdePlQ "Clone an existing skill to use it as a starting point for a new one. You can clone both base system ServiceNow skills and custom skills you have created.") * [Create a prompt](https://www.servicenow.com/docs/9Sb9G2tHYaTxJEgUaEZX0g "After you create a custom skill, create a prompt. Creating a prompt enables you to choose what skill inputs to use, as well as the type of tool.") * [Configure a skill prompt](https://www.servicenow.com/docs/bb3G~DIoOrSZ5~Ld2MJUNw "Configure your skill prompt to set the model that is used and the randomness and creativity of the response.") * [Configure skill deployment settings](https://www.servicenow.com/docs/NnJpkW5tQPC6wXy6Cur5DQ "Configure the deployment settings for the skill that you have created. The deployment settings enable you to choose where the admin can find the skill in AI Admin Hub.") * [Configure security controls for a skill](https://www.servicenow.com/docs/waDEzQpkNzung8fyrs~aPA "You must define an access control list (ACL) and role restrictions for all skills. An ACL enables you to restrict who is able to access and execute a skill to only users with the correct role. Role restrictions enable users to limit roles during skill execution.") * [Add a tool](https://www.servicenow.com/docs/F6RAMnVRqIFcWmg1BYu1oA "Add and configure tools in the AI Skill Kit tool canvas to gather data and context before a prompt runs. Tools can be chained sequentially, run in parallel, or branched conditionally using decision nodes.") * [Add a retriever](https://www.servicenow.com/docs/Kj4_IkbUmwrnB73IyaqQ7g "Add a retriever to your prompt to augment and add context to your prompts with AI search results.") * [Add a web search tool](https://www.servicenow.com/docs/~DwXXvK_Qsi1LDketuWnxg "Add a web search tool to your skill to retrieve web content and include it as context in your prompt.") * [Use prompt assistance](https://www.servicenow.com/docs/BKzZKeozPhhC_WEW8cl03A "Use prompt assistance to get a jump start with your prompt development by selecting an example from the prompt library or using ServiceNow Otto to generate one.") * [Test a prompt](https://www.servicenow.com/docs/iFT3SY_7Wm85oXlh0N7ndg "After you create a prompt for your custom skill, test the prompt template before you finalize it. Testing the prompt verifies that you’re seeing the expected prompt results before it’s activated.") * [Evaluate a prompt](https://www.servicenow.com/docs/seUSWWx6xYOAQ3Duff4jig "Use the AI Skill Kit evaluation tools to evaluate the effectiveness of your skill prompts.") * [Finalize and publish a skill](https://www.servicenow.com/docs/BJGUHiV2QSMt_6N4aFfrcQ "When you’re satisfied with your prompt, you can publish your custom skill. Publishing the skill enables a Otto admin to activate it.") {#skill-builder-admin-role__ul-skill-builder-admin-tasks} ### Special considerations {#skill-builder-admin-role__section-feature-role-considerations} This role grants access to the AI Skill Kit application and all skill authoring functionality. It does not grant the ability to activate skills in AI Admin Hub. Activating skills requires the admin role. When configuring access control lists (ACLs) for a skill, the roles you specify in the ACL determine which users can invoke the skill. The sn_skill_builder.admin role only controls who can author skills, not who can use them. To learn more about configuring skill ACLs, see [Configure security controls for a skill](https://www.servicenow.com/docs/waDEzQpkNzung8fyrs~aPA "You must define an access control list (ACL) and role restrictions for all skills. An ACL enables you to restrict who is able to access and execute a skill to only users with the correct role. Role restrictions enable users to limit roles during skill execution."). ## Skill Kit model admin (sn_skill_builder.sb_model_admin) {#ariaid-title3} Create and update custom large language models for use with AI Skill Kit. ### Contains roles {#skill-kit-model-admin-role__section-feature-role-contains-roles} None. ### Groups {#skill-kit-model-admin-role__section-feature-role-groups} None. This role is not assigned to any groups by default. ### Special considerations {#skill-kit-model-admin-role__section-feature-role-considerations} This role is only required when working with custom large language models. AI developers who use the standard Now LLM Service provider or prebuilt external LLM spokes do not need this role. To learn more about provider options when creating a skill, see [Create a skill](https://www.servicenow.com/docs/LKwxb28v59W_28ULmgLTkg "Create a custom skill for Otto. Creating a custom skill enables you to have greater flexibility with Otto's generative AI capabilities."). This role does not replace the sn_skill_builder.admin role. AI developers who create skills using custom large language models require both roles.