{"version":"2.1.299","anchor":"remote-managed-settings-failure-message-unified-new-managed","canonical_anchor":"remote-managed-settings-failure-message-unified-new-managed","heading":"Managed settings errors share one wording and report more detail","tier":"notice","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/remote-managed-settings-failure-message-unified-new-managed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Managed settings errors share one wording and report more detail\n\nFailures loading organization settings now share one message format, and usage data about where those settings came from has more detail\n\n**What**\n\nManaged settings are configuration an organization's admin pushes to Claude Code. When they fail validation, the error message is now built from one shared opening plus a reason when there is one.\n\nThe usage data Claude Code records when it loads managed settings now also says, among other things, how the managed settings file is protected, whether it pins an organization, whether the machine's settings document could not be read, whether the machine pins sign-in, and whether a refresh was forced from the machine.\n\n**Why**\n\nAdmins see one consistent error wording, and Anthropic gets more detail about where an organization's settings come from.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: org\n- Heads-up: no"}