{"version":"2.1.229","anchor":"managed-setting-to-block-command-sourced-plugins","canonical_anchor":"managed-setting-to-block-command-sourced-plugins","heading":"Managed setting to block command-sourced plugins","tier":"use","area":"Managed Settings","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229\/e\/managed-setting-to-block-command-sourced-plugins","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.229","markdown":"### Managed setting to block command-sourced plugins\n\nA managed key blocks command-sourced plugins, falling back to your existing hook restriction.\n\n**What**\n\nA new managed settings key, `disableCommandPluginSources`, stops plugins that come from a command source from being installed, updated or re-resolved. If it is unset it follows `allowManagedHooksOnly`, so an organization that already restricts hooks gets this too. Either key blocking produces a dedicated message naming both keys. Both fall back to blocking when the configured value fails validation. Only read from managed settings, so absent those, command sources stay allowed.\n\n**Details**\n\n- Gates: `policySettings.disableCommandPluginSources` and `policySettings.allowManagedHooksOnly`.\n- When blocked, the plugin is not installed or updated and its command is not run.\n\n**Evidence**\n\n`Command-sourced plugins are disabled by your organization's managed settings (disableCommandPluginSources \/ allowManagedHooksOnly). The plugin was not installed or updated and its command was not run.`\n\n- Area: Managed Settings\n- Names: `disableCommandPluginSources`, `allowManagedHooksOnly`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5"}