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:

You manage all of this from Organization → Skills & Workflows. Skills, workflows and assistants each have their own set of permissions on that page.

The permission toggles

For Skills and Workflows, the page has these toggles:

Browse Store — can members browse the store at all? If Off, the store is hidden for them.

Install from Store — can members install skills from the store for themselves? If Off, members can browse but not install.

Create — can members create their own skills from scratch? If Off, the create option is not shown.

Require Approval — store installs require admin approval before going live.

Share with Team — can members share their own skills with their whole team?

Require Permission to Share — members need admin approval before sharing with the team.

Assistants have the Create, Share with Team and Require Permission to Share toggles.

(The Browse Store, Install from Store and Require Approval toggles only appear when the store is available to your organization.)

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.

These permissions exist at both the org level and the team level. Team admins can tighten them for their team, but not loosen what you've turned off — see Team administration.

Controlling the store

Under Skill Store Access, choose which store tiers members can browse and install from: your own core skills, Official Skills (verified partner skills), and Community Skills.

Under Skill Store (org override), you can narrow the developer's catalog further. It can only narrow it — it cannot add anything the developer hasn't made available:

• Enabled — turn the store off entirely to hide it from every member.
• No list / Allowlist / Blocklist — restrict the store to a list of skills, or hide specific skills, by entering skill IDs (one per line).

Manage in Store takes you to the store view for your organization's library.

User permissions

The User permissions block controls who can author and distribute skills:

• Block upstream skills — admins in your org can block skills distributed from above.
• Author org-scope skills — admins can create skills scoped to the organization.
• Users can create skills — end users may author personal skills.
• Users can share skills — end users may share their personal skills with their team or org.

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 without requiring any user action.

To install a skill for your whole org, use Add skill in the Organization Skills list on Organization → Skills & Workflows. Skills installed here are where you configure shared credentials, so members can use them without individual setup. To install for a specific team, use the equivalent list in Team → Skills & Workflows.

To remove a skill you installed centrally, use the remove button next to it in the same list.

Distributed skills

Distributed Skills lists skills pushed by the developer. Block removes a skill for everyone in your organization; click Blocked to unblock it. A skill the developer has locked cannot be blocked. Team admins can also block skills for just their team, but they cannot unblock something your org has blocked.

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 are yours to control
• Create: Off, and Users can create skills: Off — 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