Share a custom skill to choose who can use it and who can change it. A member who has no access to a skill does not see it on the Skills tab or when typing / in Chat, and Agent0 does not load it in their runs.

Access and activation are separate. Sharing a skill lets people see it, but Agent0 loads it in their runs only once it is turned on for them. A skill you share stays off for the people you share it with until they turn it on, unless you turn it on for them.

Understand Permission Levels

Permission	Description
Read	See the skill, invoke it, turn it on or off for yourself, and see who has access to it.
Edit	Everything Read allows, plus change, rename, update from Git, and delete the skill, and change who it is shared with and whether it starts on for them.

You can share a skill with individual members, with teams, and with the Admin and Member roles. A team's access follows its membership, so a member who joins the team gets the access right away.

Admins Always Have Access

Admins have access to every custom skill, and nobody can remove it. The Admin entry is locked in Share:

Skills created in Dash0: The Admin role has Edit. This includes skills imported from a Git repository and skills Agent0 creates.
Skills managed as code: The Admin role has Read and can delete the skill, but cannot edit it. See Skills Managed as Code.

Access does not turn a skill on. Like everyone else, an admin turns a shared skill on with Enabled for you.

Who Has Access to a New Skill

The last step of creating or importing a skill is Access. It starts with these entries:

You: Edit, locked
Admin role: Edit, locked
Member role: Read

You always keep Edit on a skill you create, so you cannot change or remove your own entry. Change or remove any other entry before you select Create.

A new skill is turned on for you only. Everyone else on the list can see it, and each of them turns it on with Enabled for you on the Skills tab.

When you create a skill with Create with Agent0, Agent0 asks who to share it with as part of the draft. It suggests the Admin role at Edit and the Member role at Read. Accept the suggestion, name the members or teams to share with instead, or keep the skill to yourself and the admins. If a name matches more than one member or team, or none, Agent0 asks which one you mean. You and the admins keep Edit either way. If you tell Agent0 to save without checking back and name nobody, it uses the suggestion.

Agent0 sets access only when it creates a skill. To change who has an existing skill, share it from the Skills tab. Like any other new skill, a skill Agent0 creates is on for you and off for everyone you share it with until they turn it on.

You need Edit access to change who a skill is shared with.

Go to Settings → Agent0 → Skills.
Open the Skill actions menu next to the skill and select Share.
Search for the members, teams, or roles to add, and choose Read or Edit for each.
Select Save.

If you only have Read access, the menu shows View access instead. It lists who has access, so you know who to ask for Edit.

A change to sharing does not create a new version of the skill. The audit log records it as an update to the skill.

Turn a Shared Skill On for Others

A skill you share stays off for each person you share it with until they switch on Enabled for you. To spare a group that step, turn the skill on by default for their entry in Share. The skill is then on for everyone that entry covers, including members who join the team later.

Who can turn a skill on by default:

Admins: Any entry, including the Admin and Member roles and teams they do not belong to.
Members: Only an entry for a team they belong to, or their own entry. You also need Edit access to change sharing at all.

A member's own choice always wins. Someone who switches Enabled for you off keeps the skill off, even when an entry that covers them has it on by default. A member covered by several entries has the skill on by default when any of those entries has it on.

Remove Access

Remove the member, team, or role from the list in Share, then select Save. Removing an entry takes the skill away from them. A member who still has access through a team or a role keeps that access.

You can remove anyone except the Admin role, including the skill's creator and yourself. If you remove your own Edit access, ask an admin or someone else with Edit to share the skill with you again.

Existing Skills

Skills that existed before sharing was available keep their access. Admins can edit them, and every member can read them. They stay on for everyone who has not turned them off. Share a skill to change that.

Skills Managed as Code

You change skills created with Terraform, the Dash0 operator, or the API in code. If the definition sets no permissions, every member can read the skill and nobody can edit it in Dash0. To share it differently, set spec.permissions in the definition. Whatever the definition sets, admins can always read and delete the skill, but never edit it. A skill managed as code is on for everyone it is shared with. Each member can still turn it off for themselves.

Control Skill Sharing and Access