{"version":"2.1.309","anchor":"managed-only-settings-list-adds-hook-settings","canonical_anchor":"managed-only-settings-list-adds-hook-settings","heading":"Three hook settings join Claude Code's managed-settings list","tier":"use","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/managed-only-settings-list-adds-hook-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Three hook settings join Claude Code's managed-settings list\n\ndisableAllHooks, allowedHttpHookUrls and httpHookAllowedEnvVars now sit on the same settings list as allowManagedHooksOnly\n\n**Unclear.** It is not clear whether being on this list means these settings are now obeyed only when they come from managed settings.\n\n**What**\n\nManaged settings are settings an organization deploys to control Claude Code for its users. Claude Code keeps a list of settings that already includes `allowManagedHooksOnly` and `allowManagedPermissionRulesOnly`. Three settings about hooks have been added to that list:\n\n- `disableAllHooks`\n\n- `allowedHttpHookUrls`\n\n- `httpHookAllowedEnvVars`\n\nHooks are commands or web requests that Claude Code runs at set moments.\n\n**Why**\n\nAdministrators may be able to control hooks, including HTTP hooks, through managed settings in the same way as the settings already on this list.\n\n- Area: Managed Settings\n- Names: `allowManagedHooksOnly`, `allowManagedPermissionRulesOnly`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: org\n- Heads-up: no"}