{"version":"2.1.307","anchor":"plugin-disable-all-now-accounts-for-policy-managed-plugins-a","canonical_anchor":"plugin-disable-all-now-accounts-for-policy-managed-plugins-a","heading":"Disabling all plugins now skips policy plugins and explains what stays on","tier":"notice","area":"Plugins","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/plugin-disable-all-now-accounts-for-policy-managed-plugins-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Disabling all plugins now skips policy plugins and explains what stays on\n\nDisabling all plugins now leaves policy-enforced plugins alone and says when `--settings` keeps plugins on for this session\n\n**What**\n\nThe command that disables all plugins now handles two more cases:\n\n- Plugins enforced by managed settings, which an administrator controls, count as required and are skipped. Before, only plugins the organization required were skipped.\n\n- When plugins stay enabled because the `--settings` option keeps them on, the result says they are still enabled this session.\n\n**Why**\n\nThe result message now explains why some plugins stayed on, so you are not left wondering why the command seemed to miss them.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: both\n- Heads-up: no"}