{"version":"2.1.81","anchor":"strictpluginonlycustomization-policy-in-development","canonical_anchor":"strictpluginonlycustomization-policy-in-development","heading":"strictPluginOnlyCustomization Policy [In Development]","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.81\/e\/strictpluginonlycustomization-policy-in-development","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.81","markdown":"### strictPluginOnlyCustomization Policy [In Development]\n\n**What**\n\nNew managed settings policy that blocks non-plugin customization sources for specified surfaces (skills, hooks, etc.).\n\n**Status**\n\nAvailable in managed settings but not broadly documented.\n\n**Details**\n\n- Can be set to `true` (locks all surfaces) or an array of specific surface names (e.g., `[\"skills\", \"hooks\"]`)\n- `false` is an explicit no-lock override\n- Plugin, policySettings, built-in, builtin, and bundled sources are always allowed\n- Invalid values are logged as warnings\n\n**Evidence**\n\nPlugin-only customization policy (search for `\"strictPluginOnlyCustomization\"`)"}