{"version":"2.1.309","anchor":"managed-settings-now-carry-hooks-and-enabledplugins","canonical_anchor":"managed-settings-now-carry-hooks-and-enabledplugins","heading":"Managed settings now include hooks and enabled plugins from the policy source","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/managed-settings-now-carry-hooks-and-enabledplugins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Managed settings now include hooks and enabled plugins from the policy source\n\nThe managed settings Claude Code builds from your organization's policy now carry its hooks and enabledPlugins entries\n\n**Unclear.** It is not clear where in Claude Code these managed hooks and plugin entries take effect.\n\n**What**\n\nManaged settings are settings an organization's administrator supplies, which individual users cannot override. The managed settings Claude Code builds from the policy source now include two entries they did not carry before:\n\n- `hooks`: commands that run automatically at set points in a session\n\n- `enabledPlugins`: which plugins (add-on packages for Claude Code) are turned on or off\n\n**Why**\n\nHooks and plugin choices that an administrator sets through policy can now travel along with the rest of the managed settings.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: yes"}