{"version":"2.1.232","anchor":"warnings-when-policy-helper-settings-are-nested-in-the-wrong","canonical_anchor":"warnings-when-policy-helper-settings-are-nested-in-the-wrong","heading":"Warnings when policy helper settings are nested in the wrong place","tier":"notice","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232\/e\/warnings-when-policy-helper-settings-are-nested-in-the-wrong","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.232","markdown":"### Warnings when policy helper settings are nested in the wrong place\n\nSettings validation now warns when policy helper keys are nested where nothing reads them.\n\n**What**\n\nSettings validation now flags helper-shaped and payload-shaped keys that were put in a slot that does not read them, and each warning says the nested config will not apply from there.\n\n**Details**\n\n- Covers cases like `defaultSettings` placed on the singular `policyHelper` key, per-OS keys placed inside a single entry, and `claudeMd` placed on the helper key.\n- These are status warnings only; they do not block startup.\n\n**Evidence**\n\n`\"policyHelper\" and \"policyHelpers\" are TOP-LEVEL settings keys; nothing nests inside the singular entry. The nested config will NOT apply from here.`\n\n- Area: Managed Settings\n- Names: `policyHelpers`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}