{"version":"2.1.232","anchor":"fixed-policy-payloads-are-validated-like-managed-settings","canonical_anchor":"fixed-policy-payloads-are-validated-like-managed-settings","heading":"Fixed policy payloads are validated like managed settings","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/fixed-policy-payloads-are-validated-like-managed-settings","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Fixed policy payloads are validated like managed settings\n\nMalformed admin fallback settings payloads are caught at startup instead of silently doing nothing.\n\n**What**\n\nThe `default` and per-OS `defaultSettings` payloads inside `policyHelpers` are now parsed as managed-settings objects, so a malformed admin payload is caught at startup instead of silently doing nothing.\n\n**Details**\n\n- Any nested `policyHelper` \/ `policyHelpers` inside a payload is stripped before the rest is validated.\n- Delivered from an OS-admin policy source, a payload that does not validate stops Claude Code from starting.\n\n**Evidence**\n\n`not a valid static settings payload \u2014 Claude Code refuses to start on it when delivered from an OS-admin policy source`\n\n- Area: Managed Settings\n- Names: `policyHelpers`, `defaultSettings`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}