Managing the configuration

From the Claude system tab of the dashboard you manage the configuration items one by one: skills, rules, commands and agents, plus team hooks and custom plugins. Each control answers a different question: Does Claude see it? Who receives it? Should it still exist?

Three questions, three controls

Control	The question it answers	Effect
Active	Does Claude see it?	Off: the item stays on disk but Claude stops using it, on every machine.
Share	Who receives it?	On: every machine receives it. Off: in the Team edition it stays on your machines only; in the other editions it stops traveling.
Delete	Should it exist?	Removes it for the whole team. A maintainer can allow the name again later with Revive.

Active and Share are independent: an item can be shared but inactive, or yours only and active.

Skills in the Claude system tab as the maintainer sees them: each row has the date, the Team or Only yours label, and the Open, Active, Share and Delete controls Skills as the maintainer sees them (Team edition example).

Next to its name, each item shows the date the team published its latest change.

How to turn an item off without deleting it

Open the Claude system tab and the item’s section (for example Skills).
Turn off the Active switch on its row.

Claude stops using it on every machine, but the file stays where it is. To turn it back on, switch it on again. The Active switch has a different color from Share, so you don’t mix them up.

The Share switch decides who receives an item, and a label shows the result:

Team (green): every machine on the team receives it;
Only yours: it is on all your machines, but not on your teammates’ machines. The row is tinted, so your personal items stand out right away;
Only here: the item exists only on this machine and the team doesn’t publish it.

Turning Share off makes a team item Only yours: it leaves the shared configuration and stays on your machines. Turning it back on returns it to the whole team.

How to delete an item for the whole team

Click Delete on the item’s row.
The button changes to Confirm — deletes it everywhere: click it again within a few seconds.

The item disappears from every machine on the team at the next sync and doesn’t come back. Members don’t need to do anything.

If you need that name again later, at the bottom of each section you’ll find the Deleted by the team list, with Revive next to each name. Revive allows the name again, so the item can be created and shared again; it does not bring back the old content, which you can recover from the repository history or from a backup.

Who can do what

Actions that apply to the team (sharing, turning off for everyone, deleting) belong to the maintainer.
A member sees the same states as read-only: Active, Share and the label.
For items the team doesn’t publish, the member decides for themselves: Keep on all my machines brings the item to every machine they use, without giving it to the team; Keep only here brings it back to this machine only.

Skills as a member sees them: read-only states, an Only yours skill with the Keep only here button, and an Only here skill with the Keep on all my machines button Skills as a member sees them (sample data).

If a member wants one of their skills, or one of their edits to a team item, to become part of the shared configuration, they propose it to the maintainer: see Proposals to the team.

Custom plugins and team hooks

Custom plugins and team hooks are managed the same way: you turn them on and off, you share them or keep them only yours, and you delete them with the two-click confirmation. A hook you keep to yourself keeps working on your machines without entering the team’s settings; a plugin you keep to yourself is not added to the team’s plugins. For the full lifecycle of custom plugins see Custom plugins.