Answer: Administrators deploy managed settings that user and project settings can't override, and the key `allowManagedPermissionRulesOnly` makes managed settings the only settings source of permission rules. Additionally, `disableBypassPermissionsMode` is typically placed in managed settings to enforce organizational policy. Status: Confirmed Entry: tool/claude-code/admin-and-enterprise/managed-permission-settings Revision: 6 Digest: sha256:5463071b18a2c0f1 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:04:52Z Last changed: 2026-11-20T12:22:38Z (override behavior: — → user and project settings can't override) Last verified: 2026-11-20T12:22:38Z Next check: 2026-11-21T12:22:38Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of key for managed-only permission rules | allowManagedPermissionRulesOnly | [1] | 2026-11-20 key to enforce policy on bypass mode | disableBypassPermissionsMode | [1] | 2026-11-20 override behavior | user and project settings can't override | [1] | 2026-11-20 Sources: [1] Anthropic. "Configure permissions". https://code.claude.com/docs/en/permissions.md Role: primary. Accessed: 2026-11-20T12:22:38Z Quote: "allowManagedPermissionRulesOnly`](https://code.claude.com/docs/en/settings-reference#allowmanagedpermissionrulesonly), makes managed settings the only settings source of permission rules" (Supports: key for managed-only permission rules) Quote: "`disableBypassPermissionsMode` is typically placed in managed settings to enforce organizational policy" (Supports: key to enforce policy on bypass mode) Quote: "administrators deploy managed settings that user and project settings can't override" (Supports: override behavior) Published: 2026-11-20T10:20:26Z Snapshot SHA-256: ba42bcdce2df458db795d1bb316fecb06a710c84ab38efb3616362014bf77d01 (captured 2026-11-20T12:22:35Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. Cross-check: not-available at 2026-11-20T12:22:38Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:22:38Z Last attempt: 2026-11-20T12:22:38Z Notes and limitations: Extracted automatically from a single official source (section "Managed settings"). Related: https://latestn.com/tool/claude-code/admin-and-enterprise/managed-settings-delivery-mechanisms Which delivery mechanisms can I use to distribute Claude Code managed settings per OS? https://latestn.com/tool/claude-code/admin-and-enterprise/managed-settings-example What does an organization's managed-settings.json for Claude Code look like? https://latestn.com/tool/claude-code/admin-and-enterprise/metrics-cardinality-control How do I control metrics cardinality in Claude Code OpenTelemetry? https://latestn.com/tool/claude-code/admin-and-enterprise/how-gateway-works How does a gateway work between Claude Code and the model provider? https://latestn.com/tool/claude-code/admin-and-enterprise/launcher-process-coverage Which processes does the Claude Code corporate launcher cover, and which start outside it? https://latestn.com/tool/claude-code/admin-and-enterprise/launcher-value-format-arguments What format should the Claude Code launcher value use and how are arguments passed to it? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:22:38Z | changed | override behavior: — → user and project settings can't override | [1] 2026-11-20T12:22:38Z | changed | key to enforce policy on bypass mode: — → disableBypassPermissionsMode | [1] 2026-11-20T12:22:38Z | changed | key for managed-only permission rules: — → allowManagedPermissionRulesOnly | [1] 2026-11-20T12:22:38Z | changed | Override behavior: user and project settings can't override → — | [1] 2026-11-20T12:22:38Z | changed | Key to enforce bypass policy: disableBypassPermissionsMode → — | [1] 2026-11-20T12:22:38Z | changed | Key for managed-only permission rules: allowManagedPermissionRulesOnly → — | [1] 2026-11-19T12:18:08Z | changed | Override behavior: — → user and project settings can't override | [1] 2026-11-19T12:18:08Z | changed | Key to enforce bypass policy: — → disableBypassPermissionsMode | [1] 2026-11-19T12:18:08Z | changed | Key for managed-only permission rules: — → allowManagedPermissionRulesOnly | [1] 2026-11-19T12:18:08Z | changed | override behavior: user and project settings can't override → — | [1] 2026-11-19T12:18:08Z | changed | key to enforce bypass policy: disableBypassPermissionsMode → — | [1] 2026-11-19T12:18:08Z | changed | key for managed-only permission rules: allowManagedPermissionRulesOnly → — | [1] 2026-11-18T12:17:58Z | changed | override behavior: — → user and project settings can't override | [1] 2026-11-18T12:17:58Z | changed | key to enforce bypass policy: — → disableBypassPermissionsMode | [1] 2026-11-18T12:17:58Z | changed | key for managed-only permission rules: — → allowManagedPermissionRulesOnly | [1] 2026-11-18T12:17:58Z | changed | Override behavior: user and project settings can't override → — | [1] 2026-11-18T12:17:58Z | changed | Key to enforce bypass mode policy: disableBypassPermissionsMode → — | [1] 2026-11-18T12:17:58Z | changed | Key for managed-only permission rules: allowManagedPermissionRulesOnly → — | [1] 2026-11-15T12:22:48Z | changed | Key to enforce bypass mode policy: — → disableBypassPermissionsMode | [1] 2026-11-15T12:22:48Z | changed | Key to enforce bypass policy: disableBypassPermissionsMode → — | [1] 2026-11-14T12:18:22Z | changed | Key to enforce bypass policy: — → disableBypassPermissionsMode | [1] 2026-11-14T12:18:22Z | changed | Key for enforcing policy on bypass mode: disableBypassPermissionsMode → — | [1] 2026-11-13T03:04:52Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/admin-and-enterprise/managed-permission-settings/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/managed-permission-settings POST: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/managed-permission-settings with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/admin-and-enterprise/managed-permission-settings?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I enforce Claude Code permission rules across my organization with managed settings? Revision 6, last verified 2026-11-20T12:22:38Z. https://latestn.com/tool/claude-code/admin-and-enterprise/managed-permission-settings (accessed 2026-11-21T09:58:27Z). @misc{LatestN_tool_claude_code_admin_and_enterprise_managed_permission_settings_r6, title = {How do I enforce Claude Code permission rules across my organization with managed settings?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/admin-and-enterprise/managed-permission-settings}}, note = {Revision 6; digest sha256:5463071b18a2c0f1; last verified 2026-11-20T12:22:38Z; accessed 2026-11-21T09:58:27Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/claude-code/admin-and-enterprise/managed-permission-settings