{"version":"2.1.317","anchor":"managed-settings-can-be-left-out-of-the-policy-tier-with","canonical_anchor":"managed-settings-can-be-left-out-of-the-policy-tier-with","heading":"Settings passed with --managed-settings can now be kept out of the policy level","tier":"notice","area":"Managed Settings","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/managed-settings-can-be-left-out-of-the-policy-tier-with","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Settings passed with `--managed-settings` can now be kept out of the policy level\n\nSettings given with `--managed-settings` may now be kept out of the policy level of settings, and Claude Code logs a warning when that happens\n\n**Unclear.** It is not stated when settings passed with `--managed-settings` are kept out of the policy level.\n\n**What**\n\nClaude Code combines settings from several levels. The policy level holds settings an organization enforces. Settings passed with the `--managed-settings` flag can now be kept out of that level in some cases. When the reason for keeping them out changes, Claude Code logs a warning that begins '--managed-settings left out of the policy tier:'.\n\n**Why**\n\nIf your organization passes settings with `--managed-settings`, check for this warning. It means those settings were not applied at the policy level.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}