Skill policies
Control which skills your users can browse, install, and build.
What skills are
Skills extend what your assistant can do. A skill might connect to Salesforce, run a SQL query, send a Slack message, or pull data from an internal API. Skills installed on an assistant become tools it can use when handling tasks.
There are three sources of skills:
| Source | What it is |
|---|---|
| Marketplace | Pre-built skills published by the developer or third parties, browsable in the skills store |
| Custom | Skills users or team admins build themselves in Studio |
| System | Skills built into the platform — always available, cannot be removed |
As an org admin, you control access to marketplace and custom skills. System skills are outside your control.
The three permission levels
For both marketplace and custom skills, there are three independent permissions:
Browse store — can users see the skills marketplace at all? If Off, the marketplace tab is hidden entirely. Users don't know it exists.
Install from store — can users install marketplace skills for themselves? Requires Browse store to also be On. If Off, users can browse the marketplace but not install anything.
Create custom skills — can users open Studio and build their own skills? If Off, Studio is hidden and the create option is not shown.
These three permissions exist independently at both the org level and the team level. You can, for example, allow browsing but block installation — useful if you want users to see what's available before your IT team vets and approves specific skills centrally.
Centrally managed skills
Instead of letting each user install their own skills, some organizations prefer to install skills centrally for everyone. Org admins or team admins can install skills on behalf of their users — those skills appear in users' assistants automatically without requiring any user action.
To install a skill for all users in your org: go to Organization → Skills → Installed, browse the marketplace, and install to the org scope. The skill becomes available to every user's assistant.
To install for a specific team: go to Team settings → Skills → Installed and install to the team scope.
When a skill is installed at the org or team level, users see it as part of their assistant — they don't need to install it themselves and, depending on your policy, may not be able to remove it.
Skill approval workflow
If your developer has enabled the approval workflow, users who request to install a skill from the marketplace will trigger a review rather than installing immediately. You'll see pending requests in Organization → Skills → Pending approval.
Review each request, check the skill's permissions and data access, and approve or deny. Approved skills install immediately for the requesting user. Denied requests notify the user with an optional reason.
Scoping custom skill visibility
When a user builds a custom skill in Studio, it's private to them by default. They can share it with their team or submit it to the org marketplace for others to install. Org admins control whether submitted custom skills go through an approval step before appearing in the org marketplace — configure this in Organization → Skills → Custom skills → Require approval for org publishing.
Recommended policy for regulated industries
If your organization operates in a regulated environment (finance, healthcare, legal), consider:
- Browse store: On, Install from store: Off — users can see what exists, but installs go through your approval workflow
- Create custom skills: Off — disable Studio to prevent users from connecting unapproved external services
- Centrally install vetted skills at the org level so users still have a useful assistant without self-service installs