{"version":"2.1.295","anchor":"managed-settings-summary-now-reports-a-separate-seat-layer","canonical_anchor":"managed-settings-summary-now-reports-a-separate-seat-layer","heading":"Plugin settings summary now includes a separate seat layer","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/managed-settings-summary-now-reports-a-separate-seat-layer","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### Plugin settings summary now includes a separate seat layer\n\nThe summary of plugin and marketplace settings now includes a seat section with its own plugin and marketplace values\n\n**What**\n\nClaude Code builds a summary of the settings that control plugins (add-on packages) and marketplaces (catalogues you can install plugins from). Before, it held only `extraKnownMarketplaces` and `strictKnownMarketplaces`. It now also has a `seat` section, read from a second settings source, holding its own values for:\n\n- `enabledPlugins`\n\n- `extraKnownMarketplaces`\n\n- `strictKnownMarketplaces`\n\n**Why**\n\nThis points to a new place, tied to a seat, from which plugin and marketplace rules can come.\n\n- Area: Managed Settings\n- Names: `extraKnownMarketplaces`, `strictKnownMarketplaces`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}