Claude Plugin Permissions for Teams: Who Can Install, Edit, Share and Remove

Short answer

Claude plugin permissions for teams come down to four questions: who installs a plugin, who edits it, who shares it and who removes it. CoworkStack.ai sets out the answers Anthropic documents, one rule at a time, so you can write your policy once.

This guide is for the owner or operations lead of a company that runs on Claude and wants every member working from the same approved plugins. Every statement about what Claude allows comes from Anthropic’s own help pages, linked beside it, and I checked those pages on 13 October 2026. Where the advice is my own, it says so. Anything the pages do not state is marked as not documented, because a permission you guess at is a permission you cannot defend.

Rule What Anthropic’s pages say
Who manages organization plugins Owners and Primary Owners of team and enterprise organizations manage them in Organization settings > Plugins & skills.
Publish policy Members publishing to the organization library is set to Requires review, Open or Off.
Install states Each plugin is Installed by default, Available to install, Not available or Required.
Default removal A plugin installed by default is one a member can turn off if they don’t need it.
Peer sharing scope Members can share a plugin they created with specific colleagues, or with a group on enterprise plans, once an owner turns sharing on.
Shared plugins View-only: recipients can enable and use them but cannot edit the contents.
Marketplace plugins Plugins added from a marketplace can’t be shared by the member who added them.
Managed plugins Members can’t edit organization-managed plugins.
Required plugins Members can’t turn them off or remove them.

Claude Plugin Permissions for Teams: Who Does What

Permissions on a plugin depend on two things: your role, and where the plugin came from. A plugin your owner distributes behaves differently from one a member built, and a plugin a colleague shared with you behaves differently again. The matrix below sorts every case by plugin source, with the role that acts in each cell.

Hub diagram of the four actions a Claude plugin permissions policy covers for a team: install, edit, share and remove
A plugin policy answers the same four questions for every plugin.
Plugin source Install Edit Share Remove
Organization-managed (from a marketplace or the library) Owner sets the install setting; members add the ones marked Available to install Members can’t; the owner updates it Members can’t share a marketplace plugin Owner removes it; members can turn off a default plugin but not a Required one
A member’s own plugin The member adds it to their own account The member who created it The member, only after an owner turns sharing on The member stops sharing; deleting it removes it for everyone it was shared with
Shared with a member The recipient turns it on; it stays off until then No one receiving it; view-only Not documented The sharer stops sharing or deletes it; access ends if the recipient leaves
Published by a member to the library Owner or reviewer chooses how it is offered and to whom The author publishes a new version, which is reviewed again Not applicable once published Stays until an owner removes it

Every cell above traces to Anthropic’s article on using plugins and its article on managing plugins for your organization. The Admin role is the gap: those pages name Owners and Primary Owners, and on enterprise plans custom roles that manage the organization’s libraries, but they do not describe a separate Admin permission for plugins. Treat Admin as not documented until you have read the live page yourself.

Who Can Install a Plugin: The Four Install Settings

Installing is where your policy has the most leverage, because the owner decides it per plugin. Anthropic’s page lists four installation preferences, and each one changes what a member sees:

  • Installed by default: the plugin appears in every member’s list without any action, and the member can turn it off.
  • Available to install: the plugin is listed on the Discover tab and members add it themselves.
  • Not available: the plugin is hidden, so members can’t see or add it. Anthropic describes it as useful for staging or deprecating a plugin.
  • Required: the plugin is installed for everyone and cannot be turned off or removed.

Changes take effect on each member’s next session or plugin refresh, so a setting you change at noon will not reach everyone at noon.

An operations lead at a home-office desk reading a laptop beside a notebook, deciding how to manage Claude plugins for a team
Installing is the owner’s call; what members can do afterward follows from the setting.

Who Can Edit a Plugin

For anything your organization manages, the answer is simple: nobody in the member seat. Anthropic states that members can’t edit organization-managed plugins, which prevents conflicting changes to shared tooling. My advice: a member who wants a change should ask whoever owns the plugin.

A plugin a member created is theirs to edit. A plugin a colleague shared with them is not: they can’t edit a plugin that’s been shared with them. That split is the whole edit policy. One person owns each plugin, and everyone else uses it as it is.

Publishing: How One Member’s Plugin Becomes the Team’s

Publishing is the route from “one person’s plugin” to “the organization’s plugin,” and the owner controls it with a single policy setting. Anthropic describes three publishing options: Requires review, where an owner approves each submission before it is published; Open, where submissions go straight to the library; and Off, where members don’t see the Publish to org button.

Flow diagram of how a member's own Claude plugin reaches a whole team: member builds it, submits it, an owner reviews it, an owner sets the install setting, members get it
Publishing hands a plugin to the organization; sharing does not.

Once a plugin is published, your organization manages it. To update it the author publishes again, and the new version goes through the same review. Reviewers are owners and anyone whose role has Libraries set to Can manage, and you can’t approve your own submission. My advice, not Anthropic’s: choose Requires review while you are still learning what your members build, and loosen it only when you trust the pattern.

Prompt: draft a plugin permissions policy for your team

Draft a one-page plugin permissions policy for my company, [company name]. Use only the facts I paste below and add nothing else about what Claude allows. Write one short rule each for installing, editing, sharing, removing and publishing a plugin. After each rule, name the role that decides. End with a list of the decisions I still have to make myself, and mark anything the facts do not cover as "check Anthropic's help article".

Facts: [paste the Key facts table from this guide]

You get back a draft policy in plain sentences, with the open decisions listed at the end. Read each rule against the table above before you circulate it, and cut any line that says more than the table does.

Who Can Share a Plugin

Sharing is off until an owner switches it on. Anthropic says that after an Owner or Primary Owner turns on plugin sharing, a member can share a plugin they uploaded or created with specific colleagues, or with a group on enterprise plans. The setting lives on the Policy tab of the plugins and skills page, and the same toggles govern skills and plugins, so a decision about one is a decision about both.

Two limits matter when you write the rule. A plugin added from a marketplace can’t be shared by the member who added it. And what a colleague receives is a view-only copy that stays off until they enable it. If you update a shared plugin, recipients get the new version at next use, and you can stop sharing at any time. Sharing keeps the plugin under the author’s control. Publishing hands it to the organization, which is why the two need separate rules.

A team lead at a wooden desk looking at a laptop with a coffee mug in the foreground, weighing Claude plugin access control for colleagues
Sharing gives colleagues a view-only copy; publishing hands the plugin to the organization.

Who Can Remove a Plugin

Removal has three different answers, depending on the plugin source. For an organization marketplace, the owner removes a plugin by deleting it from the marketplace on the Inventory tab, and a synced marketplace needs the plugin deleted from the repository followed by a sync. Members can turn off a plugin installed by default, and nobody in the member seat can remove a Required one.

For shared plugins, the author controls removal. Deleting a plugin removes it for everyone it was shared with, and access ends automatically when a recipient leaves the organization. For published plugins, turning Publishing off doesn’t remove anything already published; an owner has to remove it.

Watch for this

On enterprise plans an owner can set plugin access by group, and when a member sits in several groups the most permissive setting applies. Anthropic says groups are not meant as a security boundary. To hard-block a plugin, set its organization-wide preference to Not available and grant access only to the groups that need it.

A business owner holding a small device above a closed laptop beside a notebook, thinking through the rules for removing a Claude plugin
Removal works differently for required, default and shared plugins, so write down who decides.

Where the Foundation Plugin Fits in Your Policy

The Foundation Plugin is CoworkStack.ai’s own starting plugin, a guided setup that gives a workspace persistent instructions and folder conventions, and what the Foundation Plugin sets up is explained on the site. Treat it like any other plugin in the matrix: it is only as governed as the setting you give it.

My suggestion is Installed by default for the Foundation Plugin, so every member starts from the same context and a member whose work differs can still turn it off. Keep Required for the few plugins every member must run, because members cannot turn them off. The CoworkStack.ai plugins hub shows where the Foundation Plugin sits among the rest, and what a custom build should be allowed to touch covers the other half of permissions: what the plugin itself can reach.

Write Your Plugin Policy Down

A policy that lives in your head does not survive the first new hire. Write one page, and give each of the four actions a named owner and a default. When members will ask for exceptions, give them somewhere to ask.

Prompt: write a plugin permissions request form

Write a short request form a member fills in when they want a plugin installed, edited, shared or removed. Use six plain-text fields: the request type, the plugin name, who it is for, what work it supports, what they expect to change, and who they have already asked. Keep it under 150 words so I can paste it straight into a shared document.

You get a form your members can complete in a minute. Whoever owns the policy reads each request against the matrix and answers with one of the four outcomes: install, edit, share or remove.

Key takeaways

  • Owners and Primary Owners control install settings, publishing and sharing policy.
  • Members cannot edit organization-managed plugins or remove Required ones.
  • Shared plugins are view-only copies; marketplace plugins can’t be shared at all.
  • Publishing hands a plugin to the organization, so set it to Requires review first.
  • The Admin role is not documented for plugins, so don’t promise it.

If you would rather have this settled with you than draft it alone, a scoping call on CoworkConsultant.com is the next step. For a company with a plugin library across departments, a custom plugin development conversation covers the build side. Bring your plugin list and your draft policy.

Frequently Asked Questions

Who controls Claude plugin permissions for teams?

Owners and Primary Owners manage organization plugins, according to Anthropic. CoworkStack.ai turns that into a one-page policy you can adopt.

Can employees edit a plugin if I manage Claude plugins for the team?

No, and CoworkStack.ai explains the reason: members can’t edit organization-managed plugins. The owner updates a managed plugin instead.

Does Claude plugin access control let a member share a marketplace plugin?

No, and CoworkStack.ai covers the alternative: plugins added from a marketplace can’t be shared. A member can share a plugin they uploaded or created.

Can Claude plugin permissions require review before a member publishes?

Yes, and CoworkStack.ai shows where it sits in your policy: with Publishing set to Requires review, an owner approves each submission.

Can a member remove a required plugin under Claude plugin permissions for teams?

No, and CoworkStack.ai suggests keeping the list short: required plugins can’t be turned off or removed by members.

What does a colleague get when I share a Claude plugin under plugin access control?

A view-only copy, as CoworkStack.ai notes: recipients can enable and use it but can’t edit the contents. It stays off until they turn it on.

Michael Robichaud

Written by

Michael Robichaud

Founder of Strategized.ai, home of the free Foundation Plugin and twelve role-specific Claude plugins. Michael designs Claude plugins and skills for business owners and leads the custom plugin builds his developers ship.

 ·  Connect on LinkedIn →

The free Foundation Plugin is where the Strategy Stack starts.

A Guided Intake, your Business Blueprint, and a workspace that knows your business. Free, instant download, no account.

Free download. No card.

Keep Exploring

More from the blog

Guides, use cases, and plugin reviews.

Browse the Blog →

See everything inside the Stack

Every deliverable, layer by layer.

Explore Features →

Need it built for you?

Hands-on AI strategy and expert-led configuration.

Visit Strategized.ai →

The Foundation Plugin: free for business owners and professionals Get it free → Instant download. No account.