Deploy managed settings changedmanaged-settings
Nearest release: v2.1.251, published 6 hours before this site recorded the change. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Recorded here
Lines+2added
Lines−0removed
From line
269
where the diff opens
First seen
21 Aug 2026
this site's first read of the page
Recorded edits59to this page, all time
The whole hunk
from line 269, old and new numbered
/
from line 269
269269When the policy isn't applying, the `Setting sources` line tells you which of two problems you have:
270270
271271* **The line is missing**: Claude Code found no managed source that delivers a policy key. If you deployed a managed settings file, check that it sits at the path for the OS, that it's valid JSON, and that it contains a [policy key](#how-claude-code-combines-managed-sources) rather than only the control keys.
272
273 When you deployed through server-managed settings instead, run `claude doctor`, which reports the [fetch outcome](/docs/en/server-managed-settings#verify-settings-delivery).
272274* **The line names a source other than the one you deployed**: a higher-priority source is present and Claude Code ignored yours, and `Skipped sources` lists it. [How Claude Code combines managed sources](#how-claude-code-combines-managed-sources) gives the order.
273275
274276<span id="invalid-entries-in-managed-settings" />
No line in this hunk matches that.