[DOCS] Plugin management docs missing organization-level plugin force-disable mechanism

[coygeek]

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/plugin-marketplaces

Section/Topic

Organization plugin management — the mechanism for administrators to force-disable specific installed plugins

Current Documentation

The plugin marketplaces page documents organization-level marketplace restrictions via managed settings:

• strictKnownMarketplaces — restricts which marketplaces users can access
• blockedMarketplaces — blocks specific marketplace URLs

These controls operate at the marketplace level (allowing or blocking entire sources), not at the individual plugin level.

What's Wrong or Missing?

Changelog v2.1.75 states: "Fixed managed-disabled plugins showing up in the /plugin Installed tab — plugins force-disabled by your organization are now hidden."

This reveals that organizations have a mechanism to force-disable specific individual plugins (not just restrict marketplace sources). This capability is not documented anywhere:

• The plugin marketplaces page covers marketplace-level restrictions only
• The settings page lists managed settings keys but does not include a key for disabling individual plugins
• No documentation explains how an administrator would mark a specific plugin as force-disabled

Enterprise and Team administrators who need to restrict specific plugins from their organization have no documentation to reference for this capability.

Suggested Improvement

Add a section to the plugin marketplaces page (or the managed settings section of the settings page) documenting:

1. The managed settings key or mechanism used to force-disable individual plugins
2. What happens to a force-disabled plugin from the user's perspective (hidden from Installed tab, cannot be re-enabled)
3. Example configuration showing how an admin would disable a specific plugin

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

Page	Context
https://code.claude.com/docs/en/plugin-marketplaces	Marketplace-level restrictions documented, individual plugin disable not covered
https://code.claude.com/docs/en/settings	Managed settings keys listed, no individual plugin disable key

Total scope: 2 pages affected

Source: Changelog v2.1.75 — "Fixed managed-disabled plugins showing up in the /plugin Installed tab — plugins force-disabled by your organization are now hidden"

[coygeek]

Still relevant as of 2026-03-28 after re-checking the current docs. This issue is partially resolved, but the remaining documentation gap is still present.

[coygeek]

---

Issue #34155 Verification

Title: [DOCS] Plugin management docs missing organization-level plugin force-disable mechanism
Issue Date: 2026-03-13
Verification Date: 2026-04-01
Status: PARTIALLY RESOLVED

---

Issue Summary

This issue reports that Claude Code documentation did not explain the organization-level mechanism for force-disabling specific plugins and did not clearly document the resulting user-visible behavior.

---

Verification Results

Claim 1: Current docs do not document the managed-settings key or mechanism for force-disabling a specific plugin

Status: RESOLVED

At https://code.claude.com/docs/en/settings, lines 536-545 currently say:

enabledPlugins

Controls which plugins are enabled. Format: "plugin-name@marketplace-name": true/false

• Managed settings (managed-settings.json): Organization-wide policy overrides that block installation at all scopes and hide the plugin from the marketplace

At the same page, lines 549-555 show:

"enabledPlugins": {
"code-formatter@team-tools": true,
"deployment-tools@team-tools": true,
"experimental-features@personal": false

Verdict: The settings docs now identify enabledPlugins as the per-plugin control, explicitly say it applies from managed-settings.json, and include a concrete disabled-plugin example.

---

Claim 2: The plugin marketplaces page still documents only marketplace-level restrictions, not per-plugin force-disable controls

Status: UNRESOLVED

At https://code.claude.com/docs/en/plugin-marketplaces, lines 592-600 currently say:

For organizations requiring strict control over plugin sources, administrators can restrict which plugin marketplaces users are allowed to add using the strictKnownMarketplaces setting in managed settings.

| Undefined (default) | No restrictions. Users can add any marketplace |
| Empty array [] | Complete lockdown. Users cannot add any new marketplaces |
| List of sources | Users can only add marketplaces that match the allowlist exactly |

At the same page, lines 670-675 say:

• For GitHub sources: repo is required, and ref or path must also match if specified in the allowlist
• For URL sources: the full URL must match exactly
• For hostPattern sources: the marketplace host is matched against the regex pattern
• For pathPattern sources: the marketplace's filesystem path is matched against the regex pattern

Verdict: The plugin marketplaces page still focuses on marketplace-source restrictions and does not document a per-plugin force-disable mechanism.

---

Claim 3: Current docs fully explain what users see when a plugin is force-disabled by an organization

Status: PARTIALLY RESOLVED

At https://code.claude.com/docs/en/settings, line 545 says managed settings provide:

Organization-wide policy overrides that block installation at all scopes and hide the plugin from the marketplace

At https://code.claude.com/docs/en/discover-plugins, lines 258-260 say:

You may also see plugins with managed scope—these are installed by administrators via managed settings and cannot be modified.

Run /plugin and go to the Installed tab to see your plugins grouped by scope.

At https://code.claude.com/docs/en/changelog, line 451 says:

Fixed managed-disabled plugins showing up in the /plugin Installed tab — plugins force-disabled by your organization are now hidden

Verdict: Current docs now cover several effects of managed plugin policy, but the Installed-tab hiding detail appears only in the changelog and the docs still do not give a single admin-facing explanation of what a force-disabled plugin looks like to end users or state directly that it cannot be re-enabled.

---

Current State

Claim	Status
Current docs do not document the managed-settings key or mechanism for force-disabling a specific plugin	RESOLVED
The plugin marketplaces page still documents only marketplace-level restrictions, not per-plugin force-disable controls	UNRESOLVED
Current docs fully explain what users see when a plugin is force-disabled by an organization	PARTIALLY RESOLVED

---

Suggested Fix

Add a short admin-facing subsection in the settings or plugin marketplaces docs that explicitly says administrators can set enabledPlugins["plugin-name@marketplace-name"] to false in managed-settings.json to force-disable a specific plugin, and document the user-visible effects in one place: blocked across scopes, hidden from the marketplace, hidden from the Installed tab, and not user-modifiable.

---

References

• URL: https://code.claude.com/docs/en/settings
  • Lines 536-545: Documents enabledPlugins as "plugin-name@marketplace-name": true/false and says managed settings can block installation and hide the plugin from the marketplace
  • Lines 549-555: Shows an enabledPlugins example with "experimental-features@personal": false
• URL: https://code.claude.com/docs/en/plugin-marketplaces
  • Lines 592-600: Documents strictKnownMarketplaces as a marketplace-source restriction feature
  • Lines 670-675: Describes matching rules for marketplace source types rather than per-plugin policy
• URL: https://code.claude.com/docs/en/discover-plugins
  • Lines 258-260: Says managed-scope plugins are installed by administrators, cannot be modified, and are shown in the Installed tab
• URL: https://code.claude.com/docs/en/changelog
  • Line 451: Says force-disabled plugins are hidden from the /plugin Installed tab

---

Conclusion & Recommendation

Primary Concern: The issue reported that Claude Code docs did not clearly document the organization-level mechanism for force-disabling specific plugins.

Resolution Status: PARTIALLY RESOLVED

Recommendation: KEEP OPEN

The settings page now documents enabledPlugins as the mechanism and includes a disabled-plugin example. However, the plugin marketplaces page still only covers marketplace-level restrictions, and the user-visible behavior of force-disabled plugins remains fragmented across multiple pages.

---

[coygeek]

Issue #34155 Verification

Title: [DOCS] Plugin management docs missing organization-level plugin force-disable mechanism

Field	Value
Issue Date	(original filing date not retrieved)
Verification Date	2026-04-27
Status	RESOLVED

Issue Summary

The issue reported that Claude Code's organization-level plugin force-disable mechanism was undocumented. Specifically, changelog v2.1.75 referenced "plugins force-disabled by your organization" but no docs explained how administrators could force-disable individual plugins (as opposed to restricting entire marketplaces via strictKnownMarketplaces/blockedMarketplaces).

The issue requested documentation for:

1. The managed settings key for force-disabling individual plugins
2. User-visible behavior when a plugin is force-disabled
3. Example configuration for admins

Verification Results

Claim 1: "The settings page does not include a key for disabling individual plugins"

• Status: No longer accurate
• Evidence: settings.md:562-583 now documents enabledPlugins with a dedicated section. Line 571 explicitly states managed settings enabledPlugins provides "Organization-wide policy overrides that block installation at all scopes and hide the plugin from the marketplace." The example at lines 575-582 shows "experimental-features@personal": false demonstrating plugin-level disable.
• Verdict: Resolved

Claim 2: "No documentation explains how an administrator would mark a specific plugin as force-disabled"

• Status: No longer accurate
• Evidence: The enabledPlugins section in settings.md:571 describes the managed settings behavior. Setting a plugin entry to false in managed-settings.json blocks it organization-wide. Additionally, settings.md:440 references "plugins force-enabled in managed settings enabledPlugins" in the hook configuration section, establishing the managed settings pattern.
• Verdict: Resolved

Claim 3: "The plugin marketplaces page covers marketplace-level restrictions only"

• Status: Partially still accurate
• Evidence: The plugin-marketplaces.md:606-695 "Managed marketplace restrictions" section still focuses on strictKnownMarketplaces and blockedMarketplaces. It does not cross-reference the enabledPlugins managed settings mechanism for individual plugin force-disable. However, the settings page itself now covers this, which is the natural home for settings key documentation.
• Verdict: Substantially resolved (core docs gap filled; cross-reference opportunity remains)

Claim 4: "What happens to a force-disabled plugin from the user's perspective is undocumented"

• Status: Resolved
• Evidence: settings.md:571 documents that managed enabledPlugins with false "block installation at all scopes and hide the plugin from the marketplace." Changelog entries at lines 775 and 1118 confirm the enforcement: "Plugins blocked by organization policy (managed-settings.json) can no longer be installed or enabled, and are hidden from marketplace views."
• Verdict: Resolved

Current State

Aspect	Before Issue	Current State
Settings key for plugin force-disable	Not documented	enabledPlugins with false in managed settings (settings.md:562-583)
User-visible behavior	Not documented	"Block installation at all scopes and hide the plugin from the marketplace" (settings.md:571)
Example configuration	Missing	"experimental-features@personal": false shown (settings.md:580)
Plugin marketplaces page cross-reference	Missing	Still missing (minor gap)

Suggested Fix

N/A — the core documentation gap has been addressed.

Optional improvement: The plugin-marketplaces.md "Managed marketplace restrictions" section could add a brief note cross-referencing enabledPlugins in managed settings for individual plugin-level blocking, complementing the marketplace-level controls already documented there.

References

• settings.md:562-583 — enabledPlugins documentation including managed settings behavior: https://code.claude.com/docs/en/settings#enabledplugins
• settings.md:440 — Hook configuration referencing force-enabled managed plugins: https://code.claude.com/docs/en/settings#hook-configuration
• plugin-marketplaces.md:606-695 — Managed marketplace restrictions (marketplace-level): https://code.claude.com/docs/en/plugin-marketplaces#managed-marketplace-restrictions
• Changelog v2.1.75 — "Fixed managed-disabled plugins showing up in the /plugin Installed tab"
• Changelog — "Plugins blocked by organization policy (managed-settings.json) can no longer be installed or enabled, and are hidden from marketplace views"

Conclusion & Recommendation

Aspect	Detail
Primary Concern	Organization-level plugin force-disable mechanism was undocumented
Resolution Status	Resolved — The enabledPlugins managed settings key is now documented with behavior description and configuration example
Recommendation	Close as completed. The optional cross-reference from plugin-marketplaces.md is a minor enhancement, not a documentation gap.

[github-actions]

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.