{"version":"2.1.323","anchor":"permission-asks-org-limit-reason-consent-wording-and-unve","canonical_anchor":"permission-asks-org-limit-reason-consent-wording-and-unve","heading":"More permission checks: silent declines, consent text and refused team answers","tier":"notice","area":"Permissions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/permission-asks-org-limit-reason-consent-wording-and-unve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### More permission checks: silent declines, consent text and refused team answers\n\nClaude Code can now decline some permission requests before asking, prompts can carry consent wording, and unverified team answers are refused\n\n**What**\n\nA permission prompt is the question Claude Code asks before it does something that needs your approval. Permission handling changed in several places:\n\n- A new path can decline a request before any prompt is shown.\n\n- A prompt can now carry a consent description and start on No.\n\n- The limit an organisation sets on asking is now also triggered by an organisation limit.\n\n- In a swarm, a group of Claude agents working together, a permission answer marked as unverified is refused.\n\n**Why**\n\nPermission handling is stricter. Some requests may now be turned down without a prompt, and an answer that cannot be verified no longer approves an action.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}