Skip to content
BENIBIX Learn

Managed Settings File

AI⌨️ Claude CodeConfiguration

Also known as managed-settings.json, managed settings

A file of settings that a company puts on each machine. It beats yours.

Think of it like

It is like the school's own rules. A class cannot change them.

Example

Emma's company blocks web fetches on every laptop. IT puts a managed settings file in place, and no one can turn the block off.

Why it matters

It is how a company makes a rule that holds on each machine.

Definition

The managed settings file is managed-settings.json. A company puts it in a system folder on each machine. It is at the top of the order. So your own files and flags cannot win over it, apart from a few safety keys. It is one of a few ways a company can send its settings.

Example code

json
{
  "permissions": {
    "deny": ["WebFetch"]
  },
  "allowManagedPermissionRulesOnly": true
}
On Linux the file goes in /etc/claude-code. This one blocks web fetches.

Common mistake

Trying to undo it with your own settings. A managed key wins over every file and flag you control.

Key takeaways

  1. 1
    Set by the org. A system folder.
  2. 2
    Top of the order. Cannot override.
  3. 3
    One of several ways. Also MDM, server.