{"version":"2.1.222","anchor":"model-enforcement-stays-inactive-for-the-parent-settings-sou","canonical_anchor":"model-enforcement-stays-inactive-for-the-parent-settings-sou","heading":"Model enforcement stays inactive for the parent settings source","tier":"internal","area":"Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/model-enforcement-stays-inactive-for-the-parent-settings-sou","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Model enforcement stays inactive for the parent settings source\n\nModel restrictions won't kick in when your settings come from a trusted parent source.\n\n**What**\n\nA policy view with no model keys sourced from \"parent\" is treated as cascade-trusted instead of triggering enforcement.\n\n**Details**\n\n- The `availableModels` enforcement check previously accepted only the \"hkcu\" source in this case.\n- It now also accepts \"parent\", returning `{ state: \"inactive\", cascadeTrusted: !0 }`.\n\n**Evidence**\n\n`cascadeTrusted`\n\n- Area: Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}