{"version":"2.1.305","anchor":"managed-allowmanagedpermissionrulesonly-docs-desktop-plug","canonical_anchor":"managed-rules-setting-now-affects-plugin-trust-check","heading":"allowManagedPermissionRulesOnly now limits host-delivered plugins more in Claude Desktop","tier":"notice","area":"Permissions","scope":"org","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/managed-allowmanagedpermissionrulesonly-docs-desktop-plug","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### `allowManagedPermissionRulesOnly` now limits host-delivered plugins more in Claude Desktop\n\nWhen an organization sets `allowManagedPermissionRulesOnly`, a plugin-source trust check fails and Desktop `--plugin-dir` plugins lose their allowed-tools\n\n**Unclear.** It is not clear whether Claude Code's behaviour changed or only the description of the setting.\n\n**What**\n\n`allowManagedPermissionRulesOnly` makes managed settings (settings an organization's administrator sets centrally) the only place permission rules can come from. Its handling of plugins (add-on packages) changed.\n\n- One check on whether a plugin's source is trusted now also fails when managed settings set `allowManagedPermissionRulesOnly` to true and Claude Code is in a managed mode.\n\n- The setting's description now says plugins delivered by the host app through `--plugin-dir` keep their `allowed-tools` (tools they may use without asking) only in Claude Desktop, and only while the setting is not set by the organization's own managed settings. Before, it said these plugins kept their `allowed-tools` with no such condition.\n\n**Why**\n\nIn organizations that turn this setting on, some plugins may no longer be treated as trusted, and Desktop plugins loaded with `--plugin-dir` may need to ask before using tools they previously used freely.\n\n- Area: Permissions\n- Names: `allowManagedPermissionRulesOnly`, `--plugin-dir`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: yes"}