Managing your configuration

From the dashboard’s Claude system tab you manage individual configuration items — skills, rules, commands, agents — with actions that are independent of one another. Each action answers a different question: does Claude see it? who receives it? should it exist at all?

Three questions, three controls

Control	Question it answers	Effect
Active	Does Claude see it?	Turn it off and the item stays on disk but Claude stops using it, on every one of your machines.
Share	Who receives it?	On: it goes to the whole team. Off: it is kept private — on all of your machines, never on your teammates’.
Delete	Should it exist?	Removal for the whole team; it sticks, and a maintainer can re-allow the name later with Revive.

Active and Share are independent: an item can be shared but disabled, or private and active.

The Claude system tab as the maintainer sees it (Team edition example): every item carries a Team/Private badge and the Active, Share and Delete controls.

Active and disable

Disabling an item hides it from Claude, on every machine, without removing it: the file stays where it is and you can re-enable it at any time. This is different from keeping it private — here you genuinely switch it off, whereas a private item is still used by Claude on your own machines. The toggle has a distinct color precisely so you don’t confuse it with sharing.

The Share toggle decides who receives an item, and a badge shows the result at a glance:

Team (green) — shared with everyone. At the next sync it reaches every machine in the team.
Private — kept on all of your machines, but never on your teammates’.

Turning Share off makes a team item private: it leaves the shared set and stays on your machines only. Turning it back on returns it to the whole team. This is available in the Team edition, where a dedicated repository keeps your private items separate from the team’s.

Delete — and revive

Delete removes an item for the whole team. Because it’s a team-wide action, it asks for a double-click confirmation: the first click arms the button, the second confirms.

The deletion sticks. A teammate’s machine that was behind no longer brings the item back at its next sync, and members don’t have to do anything — the item simply disappears and doesn’t return.

If you later need a deleted name back, the maintainer finds a Deleted by the team list at the bottom of each section, with a Revive button next to each name. Revive re-allows the name so the item can be created and shared again — it does not restore the old content; recover that from git history or a backup.

Who can do what

Team-wide actions — share, keep private, disable for everyone, delete — are reserved for the maintainer, who decides for the whole team.
A member sees the same states (active, and the Team/Private badge) read-only.

Custom plugins and team hooks

Custom plugins and team hooks are managed the same way: they can be enabled and disabled and deleted (always with the double-click confirmation, and always for the whole team). As with every other item, these are decisions that apply across the whole fleet and rest with the maintainer. For the full lifecycle of custom plugins — from authoring to automatic receipt — see the dedicated guide Custom plugins.