Answer: Save personal settings at ~/.claude/settings.json, team settings at .claude/settings.json at the top of the repository, and organization settings as managed-settings.json. Status: Confirmed Entry: tool/claude-code/settings/settings-file-locations Revision: 2 Digest: sha256:9f8474ca5dd91085 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:05:48Z Last changed: 2026-11-16T12:12:41Z (Organization deployment: — → managed-settings.json) Last verified: 2026-11-20T12:25:21Z Next check: 2026-11-21T12:25:21Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Personal settings location | ~/.claude/settings.json | [1] | 2026-11-20 Team settings location | .claude/settings.json | [1] | 2026-11-20 Organization settings location | managed-settings.json | [1] | 2026-11-20 Team file placement | .claude/settings.json | [1] | 2026-11-20 Organization deployment | managed-settings.json | [1] | 2026-11-20 Sources: [1] Anthropic. "Example settings files". https://code.claude.com/docs/en/settings-example.md Role: primary. Accessed: 2026-11-20T12:25:21Z Quote: "A developer's `~/.claude/settings.json`" (Supports: Personal settings location) Quote: "A team's `.claude/settings.json`, committed to the repository" (Supports: Team settings location) Quote: "An organization's `managed-settings.json`" (Supports: Organization settings location) Quote: "Save a file like this at `.claude/settings.json` at the top of the repository." (Supports: Team file placement) Quote: "Administrators deploy a file like this as `managed-settings.json`, or the same JSON through MDM or" (Supports: Organization deployment) Published: 2026-11-20T04:10:58Z Snapshot SHA-256: cac911d94631e3a20a0b720d43f6f71c3c90af796a2ff823b389e79de82aee51 (captured 2026-11-15T12:25:37Z) 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]. On this check the text of [1] was unchanged since 2026-11-15T12:25:37Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:25:21Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:25:21Z Last attempt: 2026-11-20T12:25:21Z Notes and limitations: Extracted automatically from a single official source (section "Example settings files"). Related: https://latestn.com/tool/claude-code/settings/settings-json-comments Can I put comments in a Claude Code settings.json file? https://latestn.com/tool/claude-code/settings/settings-precedence Which Claude Code settings file takes precedence when the same key is set in multiple places? https://latestn.com/tool/claude-code/settings/settings-precedence-managed-sources How does Claude Code decide which settings win when server-managed and endpoint-managed settings conflict? https://latestn.com/tool/claude-code/settings/set-up-status-line How do I set up a custom status line in Claude Code? https://latestn.com/tool/claude-code/settings/set-working-directory-sdk How do I change the working directory for a Claude Code Agent SDK session? https://latestn.com/tool/claude-code/settings/setting-sources-precedence How do I control which settings sources the Claude Code Agent SDK loads? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-16T12:12:41Z | changed | Organization deployment: — → managed-settings.json | [1] 2026-11-16T12:12:41Z | changed | Team file placement: — → .claude/settings.json | [1] 2026-11-16T12:12:41Z | changed | Organization settings deploy instruction: managed-settings.json → — | [1] 2026-11-16T12:12:41Z | changed | Team settings save instruction: .claude/settings.json → — | [1] 2026-11-16T12:12:41Z | changed | Personal settings save instruction: ~/.claude/settings.json → — | [1] 2026-11-13T03:05:48Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/claude-code/settings/settings-file-locations/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/settings/settings-file-locations POST: https://latestn.com/dispute/tool/claude-code/settings/settings-file-locations with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/claude-code/settings/settings-file-locations?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). Where do I save Claude Code settings for myself, my team, or my organization? Revision 2, last verified 2026-11-20T12:25:21Z. https://latestn.com/tool/claude-code/settings/settings-file-locations (accessed 2026-11-21T09:54:46Z). @misc{LatestN_tool_claude_code_settings_settings_file_locations_r2, title = {Where do I save Claude Code settings for myself, my team, or my organization?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/claude-code/settings/settings-file-locations}}, note = {Revision 2; digest sha256:9f8474ca5dd91085; last verified 2026-11-20T12:25:21Z; accessed 2026-11-21T09:54:46Z} } 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/settings/settings-file-locations