{"version":"2.1.228","anchor":"managed-settings-accept-per-os-policyhelpers","canonical_anchor":"managed-settings-accept-per-os-policyhelpers","heading":"Managed settings accept per-OS policyHelpers","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/managed-settings-accept-per-os-policyhelpers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Managed settings accept per-OS `policyHelpers`\n\nAdmins can set a different policy helper program per operating system with a new policyHelpers setting.\n\n**What**\n\nSettings now take a `policyHelpers` object keyed by `macos`, `linux`, `windows` and `wsl`, alongside the existing single `policyHelper`. A bad individual entry is ignored with a status warning, but a structurally invalid `policyHelpers` object coming from an OS-admin policy source stops startup.\n\n**Details**\n\n- WSL falls back to the `linux` entry under some conditions.\n- If no entry matches the current platform and there is no singular `policyHelper` fallback, a warning is emitted and no helper runs.\n\n**Evidence**\n\n`\"policyHelpers\" could not be parsed: expected an object mapping OS keys`\n\n- Area: Managed Settings\n- Names: `policyHelpers`, `policyHelper`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 3\/5"}