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 separate 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 travels to the whole team. Off: it stays on this machine only.
Private (Team edition)	On which machines?	Keeps it on all of your machines but never on your teammates’.
Delete	Should it exist?	Permanent removal, for the whole team.

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

The Claude system tab as the maintainer sees it (Team edition example): every item — skills, rules, custom plugins, team hooks — exposes the Active, Share, Make private and Delete actions.

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 not sharing it — here you genuinely switch it off, whereas an “unshared” item was still used by Claude locally. The toggle has a distinct color precisely so you don’t confuse it with sharing.

The Share toggle decides whether an item is part of the team set. On, it travels to every machine in the team at the next sync; off, it stays on this machine only.

Make private (Team edition)

Sometimes an item is only for you — but you want it on all of your machines, not just the one in front of you now. That is exactly what Private does: a badge shows whether an item is Team or Private, with the control to move it between the two.

Team — shared with everyone.
Private — present on all of your machines, never on your teammates’.

Making a team item private takes it out of the shared set and keeps it on your machines only; re-sharing it returns it to the whole team. This is available in the Team edition, where the dedicated repository that keeps your private items separate exists.

Delete

Delete removes an item permanently and for the whole team. Because it cannot be undone, it asks for a double-click confirmation: the first click arms the button, the second confirms.

Who can do what

Team-wide actions — share, disable for everyone, delete, re-share — are reserved for the maintainer, who decides for the whole team.
A member sees the same states (active, sharing, 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.