Manage Claude Code plugins for your organization - Claude Code Docs
Documentation Index Fetch the complete documentation index at: /docs/llms.txt Use this file to discover all available pages before exploring further. Skip to main content Assistant Responses are generated using AI and may contain mistakes. Managed settings let you decide which plugins Claude Code installs and allows on every machine in your organization. Users can’t override them. You deliver them either as server-managed settings from the claude.ai admin console or as endpoint-managed settings through MDM or a managed-settings.json file.
Most controls on this page take effect only from managed settings. This page is for administrators, and the settings here govern Claude Code. These cases are covered on other pages: Installing plugins for yourself : start at Install plugins Controlling which plugins members can use in claude.ai and Cowork : see Manage plugins for your organization on claude.com Rolling one plugin out to claude.ai, Cowork, and Claude Code together : see Choose a rollout route on claude.com The plugins page in claude.ai’s admin settings : Organization settings > Plugins & skills turns plugins on for members’ claude.ai accounts, and those reach Claude Code as synced plugins .
It doesn’t set any of the keys on this page The sections follow the order most rollouts take: require plugins for everyone or per repository, seed containers and CI , restrict what users can add on their own, set update policy , then audit what’s installed. To review every policy key in one place, see the control matrix . Pre-install and require plugins A marketplace is a catalog of plugins that Claude Code fetches from a git repository, a URL, or a local path.
Once you register a marketplace on a machine, Claude Code can install plugins from it. To install plugins for a fleet, set two keys together in managed settings , the policy file or server-delivered policy that every machine in your organization reads: extraKnownMarketplaces registers a marketplace on each machine, and enabledPlugins names the plugins to install and enable from it. Choose a delivery mechanism covers how managed settings reach each machine.
Choose a delivery mechanism Managed settings reach a machine through one of three delivery mechanisms: Server-managed settings : set the plugin keys as JSON at Organization settings > Claude Code > Managed settings . Requires an Owner role in your Claude organization. A cloud session fetches these settings before it installs plugins. MDM policies : on macOS, deliver a plist whose top-level keys are the settings keys. On Windows, store the whole JSON document as a string in a registry value.
The plist domain and the registry key are in Where each mechanism stores the policy . Managed settings file : place a managed-settings.json at the platform’s system path. You can also add files to the managed-settings.d/ drop-in directory beside it. The file paths per platform are in Where each mechanism stores the policy , and the drop-in merge rules are in Split a file-based policy across teams . Use server-managed settings if you have a Claude for Teams or Enterprise organization on claude.ai and your devices aren’t all under MDM.
Otherwise use an MDM policy or the managed settings file. For the trade-off, see Choose between server-managed and endpoint-managed settings . Which managed source applies on a machine By default, only one of these three sources applies on a machine. Claude Code uses the first that delivers a policy key, checking server-managed settings first, then MDM policies, then the managed settings file. If server-managed settings deliver even one unrelated policy key, Claude Code ignores the plugin keys in an MDM policy or managed settings file on that machine, apart from the keys it reads from every source .
To apply every source instead, set managedSourcesBehavior to "merge" . How Claude Code combines managed sources also lists the keys Claude Code reads from every source in both modes. Require a marketplace and its plugins Add the marketplace under extraKnownMarketplaces , keyed by the marketplace’s own name from its marketplace.json . Then add each plugin under enabledPlugins as plugin-name@marketplace-name . Each marketplace entry carries a source object with a source field naming the type, such as github .
This managed settings example registers an organization marketplace and force-enables two plugins from it: { "extraKnownMarketplaces" : { "your-marketplace" : { "source" : { "source" : "github" , "repo" : "your-org/your-marketplace" }, "autoUpdate" : true } }, "enabledPlugins" : { "code-formatter@your-marketplace" : true , "deploy-helper@your-marketplace" : true } } After the settings reach a machine, Claude Code registers the marketplace and installs the two plugins at the start of the user’s next session.
Users see them in /plugin , and disabling one at their own scope doesn’t stop it from loading, because managed settings take precedence over every other scope. To block a plugin at every scope and hide it from the marketplace listing, set it to false in the managed enabledPlugins instead. Adjust the autoUpdate and source fields for your marketplace: autoUpdate : true keeps the marketplace and its plugins refreshing in the background, and false turns that off.
See Set update policy . source : github is one of several source types. A git source takes a url for GitLab or an internal host, and a url source takes the address of a hosted marketplace.json . Every source shape is in the marketplace reference . If the marketplace is a private git repository, each user needs read access to it. The clone of a git-based marketplace runs with git on the user’s machine, using stored credentials and no prompts.
For users without git-host accounts, use a seed instead. A managed entry also overrides a same-name marketplace entry or --plugin-dir copy from another source: Marketplaces : a managed marketplace entry replaces a lower-precedence entry with the same name, and the two entries’ fields don’t merge. --plugin-dir copies : --plugin-dir loads a plugin from a local directory for one session. For what happens when that copy’s name matches a plugin your managed enabledPlugins names, see Name conflicts .
Anthropic’s official marketplace claude-plugins-official needs no extraKnownMarketplaces entry when enabledPlugins sets one of its plugins to true . That name@claude-plugins-official entry declares the marketplace by itself, wherever these keys apply. If you enable none of its plugins and still want it registered on every machine, give it an explicit entry, as Allow the official marketplace and your own does. Require plugins per repository To cover one repository’s contributors instead of your whole fleet, set extraKnownMarketplaces and enabledPlugins in that repository’s .claude/settings.json .
The extraKnownMarketplaces entries apply only in a folder the contributor has trusted, and in an untrusted folder Claude Code ignores them without a message: Interactive sessions : Claude Code registers the marketplace only after the contributor accepts the workspace trust dialog for that folder. Non-interactive -p runs : the entries apply only in a folder whose trust the user already accepted interactively, or whose hasTrustDialogAccepted flag you set in ~/.claude.json .
Setting enabledPlugins in the repository doesn’t install the plugin. Once the marketplace is registered, ask each contributor to run claude plugin install <name>@<marketplace> --scope project . Until they do, the /plugin Errors tab can show a line ending in isn't installed here . Contributors don’t need the install when a local directory or file marketplace lists the plugin with a relative-path source . If you use a local directory or file source with a relative path, the path resolves against your repository’s main checkout.
When you run Claude Code from a git worktree, the path still points at the main checkout, so all worktrees share the same marketplac
The rest of this page is on the live site.