{"version":"2.1.321","anchor":"marketplace-entries-record-that-managed-settings-declared-th","canonical_anchor":"marketplace-entries-record-that-managed-settings-declared-th","heading":"Plugin data survives when your organization moves its plugin marketplace","tier":"internal","area":"Plugins","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/marketplace-entries-record-that-managed-settings-declared-th","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Plugin data survives when your organization moves its plugin marketplace\n\nMarketplaces set by managed settings are now marked, so a later change of source counts as a move and plugins keep what they saved\n\n**What**\n\nA marketplace is a catalogue Claude Code installs plugins from. Managed settings are settings an organization's administrator sets for everyone. Claude Code's record of known marketplaces now has an optional `declaredByManagedSettings` field, which marks a marketplace whose source was set by managed settings.\n\nIf managed settings later name a different source for the same marketplace, Claude Code treats that as the organization moving its marketplace, and what its plugins had saved is kept.\n\n**Why**\n\nWhen an organization changes where its plugin marketplace lives, users should not lose the data their plugins had stored.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}