{"version":"2.1.282","anchor":"policy-scoped-feature-enablement-now-requires-adminparent-c","canonical_anchor":"policy-scoped-feature-enablement-now-requires-adminparent-c","heading":"Only administrator-controlled policy can switch on policy-only features","tier":"notice","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/policy-scoped-feature-enablement-now-requires-adminparent-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### Only administrator-controlled policy can switch on policy-only features\n\nPolicy settings can now switch on certain features only when they come from an administrator-owned or parent-supplied source\n\n**Unclear.** Which features are switched on this way is not known.\n\n**What**\n\nSome features can be switched on through managed policy settings, the settings an organization's administrator installs. Previously policy settings counted for this unless they came from the per-user part of the Windows registry.\n\nNow they count only when the policy comes from a location owned by an administrator, or is supplied by a parent program.\n\n**Why**\n\nPolicy settings stored somewhere an ordinary user can write to can no longer switch on features meant to be controlled by managed policy.\n\n- Area: Managed Settings\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}