By Vero SecurityBuilt and funded by Vero Security, the AI Security Engineering platform.Read the charter

Claude Code managed settings

Claude Code reads managed settings from a system file, MDM profiles or server-managed settings fetched from the admin console, and they sit at the top of the precedence stack. Managed keys can lock permission rules, disable risky modes, and restrict MCP servers and plugin marketplaces. Users can run /status to see which managed source is in force.

Read in this order

  1. OfficialClaude Code: Deploy managed settingsStart here: file locations, MDM delivery and the keys you can lock.
  2. OfficialClaude Code: Configure server-managed settingsPushing policy from the admin console with no device management.
  3. OfficialClaude Code: Settings files and precedenceThe precedence order, so you know what managed settings override.

Save your progress

We email you a sign-in link. No password.

By signing in you agree to the terms. The privacy policy explains how we use your details.

Join the AI security engineering community

Free. Roadmap updates, chapters near you, and first word when credentials open.

We’ll email you community updates. Unsubscribe anytime. By sending this you agree to the terms. The privacy policy explains how we use your details.