{"version":"2.1.286","anchor":"protected-path-set-now-includes-managed-settings-and-policy","canonical_anchor":"protected-path-set-now-includes-managed-settings-and-policy","heading":"Managed settings and policy folders are listed as protected paths","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/protected-path-set-now-includes-managed-settings-and-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Managed settings and policy folders are listed as protected paths\n\nClaude Code now lists the managed settings folder, managed-settings.d and policy settings paths among the paths it protects\n\n**Unclear.** It is not clear whether the new protected-path list is actually used by the write check yet.\n\n**What**\n\nManaged settings are settings an administrator sets for everyone on a machine or in an organisation, stored in files such as `managed-settings.json` and the `managed-settings.d\/` folder. Claude Code now has a list of protected paths that includes the managed settings folder, `managed-settings.d\/` and the policy settings paths.\n\nThe check that decides whether Claude may write to a file also has a new early step that can give an answer before the rest of the check runs.\n\n**Why**\n\nThis could stop Claude from editing managed settings files.\n\n- Area: Managed Settings\n- Names: `managed-settings.json`, `managed-settings.d\/`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}