Claude CodeIntermediateClaude Code
Pick the config scope by asking who owns it
Before touching a settings file, decide who controls the rule and who it affects: the right scope falls out on its own.
Claude Code reads config from four scopes: Managed (deployed by IT, cannot be overridden), Local, Project and User. When resolving a value the first one that appears wins, with the CLI flags sitting between Managed and Local. Exception: allow and deny lists are merged across scopes. A local allow adds, but it cannot remove a deny from the project or from Managed.
Example
Precedence (highest to lowest): 1. Managed (MDM / system file) 2. CLI flags (--model, --allowedTools) 3. Local -> .claude/settings.local.json 4. Project -> .claude/settings.json 5. User -> ~/.claude/settings.json Questions to choose: who controls this? who does it affect? can it be overridden?