{"version":"2.1.282","anchor":"status-shows-when-permission-rules-are-limited-to-managed-s","canonical_anchor":"status-shows-when-permission-rules-are-limited-to-managed-s","heading":"\/status explains when only managed permission rules apply","tier":"use","area":"Permissions","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282\/e\/status-shows-when-permission-rules-are-limited-to-managed-s","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.282","markdown":"### `\/status` explains when only managed permission rules apply\n\nWhen an organisation limits permission rules to managed settings, `\/status` now shows a row listing any allowed tools that were ignored\n\n**Unclear.** It is not confirmed that this panel is the one opened by `\/status`.\n\n**What**\n\nAn organisation can use managed settings, which are settings controlled by an administrator, to set `allowManagedPermissionRulesOnly`. When that is set, only the administrator's permission rules count. Permission rules decide which tools Claude Code may use without asking. With this setting on, the status panel now shows a \"Permission rules\" row. The row lists any allowed tools that were ignored in this session.\n\n**Why**\n\nIf you allowed tools yourself, for example with `--allowedTools`, and they had no effect, this row tells you why.\n\n- Area: Permissions\n- Names: `\/status`, `allowManagedPermissionRulesOnly`\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 1\/5"}