{"version":"2.1.309","anchor":"hook-policy-settings-now-survive-an-unconfirmed-policy-tier","canonical_anchor":"hook-policy-settings-now-survive-an-unconfirmed-policy-tier","heading":"Hook restrictions are kept while the organisation's policy is unconfirmed","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/hook-policy-settings-now-survive-an-unconfirmed-policy-tier","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Hook restrictions are kept while the organisation's policy is unconfirmed\n\ndisableAllHooks, allowedHttpHookUrls and httpHookAllowedEnvVars are no longer dropped while Claude Code's server policy tier is unconfirmed\n\n**What**\n\nManaged settings are rules an organisation's administrator sets for Claude Code. While Claude Code cannot yet confirm which policy level the server assigns (a state it calls \"unconfirmed\"), it keeps only a fixed list of these settings and drops the rest. Three hook settings have been added to that list:\n\n- `disableAllHooks`: turns off hooks, which are commands that run automatically at set points\n\n- `allowedHttpHookUrls`: limits which web addresses HTTP hooks can send to\n\n- `httpHookAllowedEnvVars`: limits which environment variables HTTP hooks can put in their headers\n\nBefore this change, all three were dropped in that state.\n\n**Why**\n\nHook restrictions an administrator has set now stay in place even while Claude Code is still waiting to confirm the policy, instead of lapsing during that time.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}