{"version":"2.1.302","anchor":"managed-policy-plugin-options-extracted-by-a-new-helper","canonical_anchor":"managed-policy-plugin-options-extracted-by-a-new-helper","heading":"Organization policy plugin options are filtered by a different check","tier":"internal","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302\/e\/managed-policy-plugin-options-extracted-by-a-new-helper","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.302","markdown":"### Organization policy plugin options are filtered by a different check\n\nClaude Code changed how it decides which plugin option values from organization policy are kept, and sets none when no values pass\n\n**Unclear.** Which policy plugin option values are now kept or dropped compared with before is not shown.\n\n**What**\n\nAn organization's administrator can set managed settings, which apply to everyone in the organization. These can include `pluginConfigs`, the stored answers to a plugin's configuration dialog. Claude Code changed how it decides which of these option values from policy to keep. It now uses a different check, and if no values pass, it sets no plugin configuration at all instead of an empty one. A built-in plugin name, `sec-default@builtin`, appears alongside this code.\n\n**Why**\n\nThe option values that survive from an organization's policy may differ from before.\n\n- Area: Managed Settings\n- Names: `pluginConfigs`\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no"}