How to manage Claude Code plugins for your organization
You manage Claude Code plugins for your organization through managed settings, the policy every machine reads and no developer can override. Four jobs cover almost every rollout: require the plugins everyone needs, restrict where plugins can come from, set an update policy, and audit what is installed. Each job maps to a small set of settings keys, and most of them only take effect from managed settings, not from a developer's own settings file.
I call this the CCC Plugin Gate: install, restrict, close the side door, update, audit. The order matters. If you restrict before you register your own marketplace, you can lock your developers out of the very plugins you meant to give them.
Pick how the policy reaches each machine
Plugin keys travel the same way as the rest of your managed settings. There are three delivery mechanisms, and by default only one applies on a given machine.
Three ways to deliver plugin policy
| Mechanism | How it works | Best for |
|---|---|---|
| Server-managed settings | JSON in the claude.ai admin console under Organization settings, Claude Code, Managed settings. Needs the Owner role | Teams or Enterprise organizations whose devices are not all under MDM |
| MDM policy | A plist on macOS whose top-level keys are the settings keys, or the whole JSON as a string in a Windows registry value | Fleets already managed by device management |
| Managed settings file | A managed-settings.json at the system path, with optional drop-in files in managed-settings.d | Servers, containers and fleets without MDM |
Watch the precedence. Claude Code uses the first source that delivers a policy key, checking server-managed settings first, then MDM, then the file. If the admin console delivers even one unrelated key, Claude Code ignores the plugin keys in your MDM policy or file on that machine. Set managedSourcesBehavior to "merge" if you need every source applied.
Step 1: Require the plugins everyone needs
Set two keys together. extraKnownMarketplaces registers a marketplace on each machine, keyed by the name in that marketplace's marketplace.json. enabledPlugins names each plugin as plugin-name@marketplace-name. Set a plugin to true to force-enable it, or false to block it at every scope and hide it from the listing.
- After the policy arrives, Claude Code registers the marketplace and installs the plugins at the start of the developer's next session. Disabling a force-enabled plugin at their own scope does not stop it loading.
- A private git marketplace needs read access for every developer. Claude Code clones it with the git credentials already stored on their machine and does not prompt.
- The official marketplace, claude-plugins-official, needs no extraKnownMarketplaces entry once enabledPlugins sets one of its plugins to true.
- For a single repository instead of the whole fleet, put the same two keys in that repo's .claude/settings.json. The marketplace only registers after the developer trusts the folder, and each contributor still runs claude plugin install with --scope project.
In CI and claude -p runs, plugins install in the background, so one can be missing from the first turn. Set CLAUDE_CODE_SYNC_PLUGIN_INSTALL=1 to make the run wait. For container images and runners that cannot clone at runtime, build a seed directory instead: install into it with CLAUDE_CODE_PLUGIN_CACHE_DIR at build time, point CLAUDE_CODE_PLUGIN_SEED_DIR at it in the image, and still list the plugins in enabledPlugins. The devcontainer guide and GitHub Actions guide cover those environments.
Step 2: Restrict where plugins can come from
strictKnownMarketplaces is an allowlist of marketplace sources, and blockedMarketplaces is a blocklist checked first. Both match the source a marketplace is fetched from, such as a GitHub repo, a git URL or a local path, not the individual plugins inside it. Both apply before anything downloads and again at session start, so an installed plugin whose marketplace no longer matches stops loading.
Allowlist entry types
| Entry | Example | Matches |
|---|---|---|
| github | { "source": "github", "repo": "your-org/approved-plugins" } | That repo, with ref and path matching exactly |
| github owner wildcard | { "source": "github", "repo": "your-org/*" } | Every repo under the owner. Needs v2.1.223 or later |
| git | { "source": "git", "url": "https://gitlab.example.com/tools/plugins.git" } | That exact URL |
| hostPattern | { "source": "hostPattern", "hostPattern": "^github\\.example\\.com$" } | Any marketplace on that host, as a regular expression |
| skills-dir | { "source": "skills-dir" } | No marketplace. It keeps skills-directory plugins loading |
Allowlist matching is strict. An entry without a ref does not cover a source that pins ref main, a github entry does not cover a git URL that clones the same repo, and a trailing slash or .git suffix counts as a different value. When a marketplace can be cloned more than one way, use a hostPattern entry. The GitHub Enterprise Server post has a worked hostPattern example.
Step 3: Close the side door with disableSideloadFlags
The allowlist does not cover plugins loaded straight from a folder. Set disableSideloadFlags to true and Claude Code rejects --plugin-dir, --plugin-url, --agents and folders named in CLAUDE_CODE_PLUGIN_DIRS at startup. It also rejects --mcp-config unless every server in it is an in-process SDK entry.
Here is the policy I would ship first. It allows the official marketplace and every repo under your GitHub org, registers both on every machine, force-enables two plugins, keeps skills-directory plugins working and closes sideloading:
- strictKnownMarketplaces: the anthropics/claude-plugins-official repo, your-org/*, and a skills-dir entry
- extraKnownMarketplaces: claude-plugins-official and your-marketplace, each with its github source
- enabledPlugins: code-formatter@your-marketplace and deploy-helper@your-marketplace set to true
- disableSideloadFlags: true
With that in place, adding any other marketplace fails with a message containing "is blocked by enterprise policy" plus the allowed sources, and claude --plugin-dir exits with a message naming disableSideloadFlags. Note what it still does not touch: .mcp.json files and claude mcp add. Pair it with allowedMcpServers from managed MCP.
Two more keys for tighter shops. strictPluginOnlyCustomization blocks skills, agents, hooks and MCP servers from user and project sources, so only plugins can add them. syncClaudeAiPlugins set to false stops Claude Code loading the plugins each person has turned on in their claude.ai account, which an empty allowlist does not cover.
Step 4: Set the update policy
Set autoUpdate to true or false on each managed extraKnownMarketplaces entry. When you set it, developers cannot flip it in /plugin. To stop plugin auto-update for every marketplace, put DISABLE_AUTOUPDATER: "1" in the managed env block. That also stops Claude Code's own updates, so add FORCE_AUTOUPDATE_PLUGINS: "1" if you only want to freeze the app.
If you want a stable group and an early-access group, host two marketplaces that point at different refs of the same plugins and give each group its own settings. On Enterprise you can do that per group in the admin console. A group's configuration does not merge with the organization-wide one, so list every marketplace the group needs, not just its channel.
Step 5: Verify and audit
- On one machine, run /status and check that Setting sources shows Enterprise managed settings. Then open /plugin and confirm the marketplace and plugins are listed. In the desktop app's Code tab, the plugin browser is under the + button next to the prompt box.
- In CI, run claude -p with --output-format stream-json --verbose. The init event lists the loaded plugins.
- For the fleet, OpenTelemetry records claude_code.plugin_installed and claude_code.plugin_loaded. Third-party plugin names are redacted unless you set OTEL_LOG_TOOL_DETAILS=1. The OpenTelemetry guide covers the export.
- On Enterprise, the Analytics API returns per-plugin, per-day install and invocation counts, grouped by user or group if you want.
What plugin policy cannot do
Requests security teams make, and the nearest control
| Request | Nearest control |
|---|---|
| Different policy per user or group | Deliver each group its own settings. Every plugin key applies to everyone who receives it |
| Block one plugin inside an allowed marketplace | Set that plugin to false in managed enabledPlugins |
| Hide the /plugin command | No key does this. Allow only your marketplace, force-enable your plugins and set disableSideloadFlags |
| Enforce the claude.ai plugin toggles here | Those reach Claude Code as synced plugins, controlled by syncClaudeAiPlugins |
When something breaks, check three things. A managed-settings.json that is not valid JSON stops Claude Code from starting and names the file. A missing Enterprise managed settings line in /status means the source never loaded. And a plugin a developer disabled that still loads is almost always force-enabled by your managed enabledPlugins.
Short, practical drops on skills, MCP, agents, prompts, and more. No spam, unsubscribe anytime.
Frequently asked questions
How do I install a Claude Code plugin for my whole organization?
Add the marketplace under extraKnownMarketplaces and the plugin under enabledPlugins as plugin-name@marketplace-name set to true, in managed settings. Claude Code installs it at the start of each developer's next session.
How do I stop developers installing plugins from unapproved marketplaces?
Set strictKnownMarketplaces in managed settings to the marketplace sources you approve, and add blockedMarketplaces for anything you want explicitly refused. Add disableSideloadFlags so nobody loads a plugin from a local folder instead.
Does an empty strictKnownMarketplaces block the official marketplace?
Yes. An empty allowlist blocks every marketplace source, including the official one. It does not block plugins synced from claude.ai accounts, which need syncClaudeAiPlugins set to false.
Why did skills-directory plugins stop loading after I set an allowlist?
Any allowlist without a { "source": "skills-dir" } entry stops plugins kept in skills folders with a plugin.json from loading. Add that entry to the allowlist.
Can I block one plugin without blocking its whole marketplace?
Yes. Set that plugin to false in managed enabledPlugins. It is blocked at every scope and hidden from the marketplace listing.
How do I get plugins into CI or containers without git access?
Build a seed directory at image build time with CLAUDE_CODE_PLUGIN_CACHE_DIR, point CLAUDE_CODE_PLUGIN_SEED_DIR at it at runtime, and list the plugins in enabledPlugins. Claude Code loads them from the seed without cloning.
Last reviewed by David Iya on November 13, 2026


