Skip to main content

Edit your policy

After you apply a template, you land in the editor. This is where you review and fine-tune the policy before exporting it. The toolbar at the top has two tabs — Form and JSON — plus Change template and Export buttons.

The two tabs stay in sync: edits in the Form update the JSON, and edits in the JSON update the Form. Switch between them freely.

Form tab​

The Form tab is a guided, no-code editor. Settings are organized into collapsible sections with a side navigation that highlights the section you're currently viewing. Each section explains what it controls and links to the relevant part of the Claude Code settings reference.

Available sections include:

  • Permissions — default permission mode plus allow, ask, and deny rules for tools and shell commands.
  • MCP servers — managed-only enforcement, allowed servers, and project-server behavior.
  • Model configuration — default model, available-models allowlist, reasoning effort, and fallback models.
  • Hooks — managed hooks and allowed HTTP hook URLs.
  • Plugins — plugin trust messaging.
  • General settings — auto-updates channel, session cleanup period, and response language.
  • Attribution settings — commit and PR attribution and the PR URL template.
  • Authentication helpers — required login method, API key helper, required org UUIDs, and cloud auth scripts.
  • Company announcements — messages shown to users at startup.
  • Display & UX — view/output style, editor mode, notifications, status line, spinner, and footer links.
  • Sandbox — sandbox enablement and excluded commands.
  • AWS & cloud credentials — auth refresh and credential export helper scripts.
  • Environment variables — environment variables applied to Claude Code sessions.

Only the settings you actually configure are written into the policy, keeping the exported file minimal.

JSON tab​

The JSON tab exposes the raw managed-settings.json. It's a full code editor with schema-aware autocomplete and validation against the official Claude Code settings schema.

  • A status line beneath the editor shows Valid JSON when the policy is well-formed, or the specific parse error when it isn't.
  • Use Clear all (top-right) to reset the policy back to an empty {}. You'll be asked to confirm before anything is cleared.
caution

If the JSON is invalid, the Form tab can't render and exporting is blocked until you fix it. The error message points you to what needs correcting.

Change the template​

Click Change template to reopen the template dialog. Applying a new selection replaces the current policy with the freshly merged template.

Next step​

When the policy looks right, continue to Export & deploy.

On this page