[DOCS] `pluginSuggestionMarketplaces` managed setting is missing from settings and marketplace policy docs

Open 💬 1 comment Opened May 27, 2026 by coygeek

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/settings

Section/Topic

Managed settings reference for plugin marketplace policy, especially the managed-settings keys that control plugin marketplace behavior

Current Documentation

The settings reference currently documents adjacent marketplace policy keys, but not pluginSuggestionMarketplaces:

| blockedMarketplaces | (Managed settings only) Blocklist of marketplace sources. Enforced on marketplace add and on plugin install, update, refresh, and auto-update, so a marketplace added before the policy was set cannot be used to fetch plugins. Blocked sources are checked before downloading, so they never touch the filesystem. See Managed marketplace restrictions |
| pluginTrustMessage | (Managed settings only) Custom message appended to the plugin trust warning shown before installation. Use this to add organization-specific context, for example to confirm that plugins from your internal marketplace are vetted. |
| strictKnownMarketplaces | (Managed settings only) Allowlist of plugin marketplace sources. Undefined = no restrictions, empty array = lockdown. Enforced on marketplace add and on plugin install, update, refresh, and auto-update, so a marketplace added before the policy was set cannot be used to fetch plugins. See Managed marketplace restrictions |

The user-facing plugin marketplace policy guide also covers only add/install restrictions:

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.
strictKnownMarketplaces restricts what users can add, but does not register marketplaces on its own. To make allowed marketplaces available automatically without users running /plugin marketplace add, pair it with extraKnownMarketplaces in the same managed-settings.json.

Meanwhile the v2.1.152 changelog announces a new managed setting:

Added pluginSuggestionMarketplaces managed setting: admins can allowlist org marketplaces whose plugins may be suggested via context-aware tips

What's Wrong or Missing?

The docs now describe marketplace policy for adding, blocking, pre-registering, and trusting marketplaces, but they do not describe the newly added pluginSuggestionMarketplaces managed setting from v2.1.152.

That leaves administrators without documentation for:

A. What the setting does

The changelog says it allowlists organization marketplaces whose plugins may be suggested via context-aware tips, but the settings reference does not define the key, accepted shape, or scope.

B. How it relates to existing marketplace controls

The current docs explain strictKnownMarketplaces, blockedMarketplaces, extraKnownMarketplaces, and pluginTrustMessage, but do not explain how pluginSuggestionMarketplaces interacts with those controls or when an admin would use it instead of broader marketplace allowlisting.

C. Where admins should configure it

admin-setup links administrators to plugin marketplace controls, but that page currently lists only strictKnownMarketplaces and blockedMarketplaces, so readers do not discover the new suggestion-specific policy surface.

Suggested Improvement

Add pluginSuggestionMarketplaces to the managed settings reference in https://code.claude.com/docs/en/settings with the same level of detail given to nearby marketplace keys:

  • State that it is managed-settings-only
  • Define the value format and what counts as a matching marketplace
  • Explain that it controls which organization marketplaces can appear in context-aware plugin suggestions
  • Clarify how it relates to strictKnownMarketplaces, blockedMarketplaces, and extraKnownMarketplaces

Also update the marketplace/admin policy pages to mention suggestion allowlisting as a separate control surface. A minimal fix would be:

  1. Add a new row for pluginSuggestionMarketplaces in the settings reference table.
  2. Add a short note in https://code.claude.com/docs/en/plugin-marketplaces under managed marketplace restrictions describing suggestion allowlisting.
  3. Add pluginSuggestionMarketplaces to the plugin marketplace control row in https://code.claude.com/docs/en/admin-setup.

Impact

Medium - Makes feature difficult to understand

Additional Context

Affected Pages:

| Page | Line(s) | Context |
|------|---------|---------|
| https://code.claude.com/docs/en/settings | 192, 233, 250 | Managed marketplace policy keys are documented, but pluginSuggestionMarketplaces is absent from the settings reference |
| https://code.claude.com/docs/en/plugin-marketplaces | 612-699 | Managed marketplace restrictions section covers add/install policy and related keys, but not suggestion allowlisting |
| https://code.claude.com/docs/en/admin-setup | 77 | Admin control matrix lists plugin marketplace control as strictKnownMarketplaces, blockedMarketplaces only |
| https://code.claude.com/docs/en/changelog | 20 | v2.1.152 changelog announces pluginSuggestionMarketplaces |

Total scope: 4 pages affected

Version context: this gap appears after the v2.1.152 release note added pluginSuggestionMarketplaces.

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗