Scope Disclosure
Scope disclosure is an AI UX pattern that states in plain language which accounts, files, tools, and actions an agent can reach, at connect time, on demand, and when scope changes. It turns permissions into a readable contract instead of a buried OAuth dump.
When to use
Essential for AI agents, OAuth-based assistants, and any system that acts on behalf of users, where plain-language scope disclosure builds trust and reduces post-hoc security risk.
When not to use
- Local toys with no external permissions to disclose.
- When legal requires full policy text but you never provide a short summary (always give both).
- One-time scripts with no retained agent identity.
Anti-patterns
- Allow-all modals with no capability list.
- Disclosing scope once at install and never again after expansion.
- Jargon-only scopes (“access user.info.email.write”) with no human translation.
- No place in settings to re-read current scope.
How products use it
| Product | Implementation |
|---|---|
| ChatGPT connectors | Permission summaries when linking apps and mail. |
| Claude connectors / computer use | Capability boundaries explained around tools and browsing. |
| GitHub Apps / OAuth | Scope lists at install with account-level review. |
| Enterprise AI gateways | Admin-visible agent capability contracts per team. |
Use this pattern in your project
Copy this prompt to generate a production-ready implementation in Cursor, Claude Code, Lovable, or any AI coding agent.
Generate a production-ready implementation of the "Scope Disclosure" AI interface design pattern.
Pattern Definition:Settings → Agents
Inbox assistant
Not connected yet. Link a mailbox to get started.
Gmail
Work inbox · [email protected]
Frequently asked questions
What is scope disclosure for AI agents?
Scope disclosure is a plain-language summary of what an agent can access and do, shown when connecting, available later in settings, and repeated when permissions grow.
When should scope be shown again?
At first grant, whenever scope expands, and on a review cadence for long-lived agents. Do not assume users remember a modal from months ago.
How does scope disclosure differ from granular consent?
Disclosure explains the contract. Granular consent lets users change it capability by capability. Ship explanation and controls together.
Related patterns
- Trust
Progress Steps
Collapsible thinking and tool traces
- Trust
Citation Tooltips
Hover for source
- Trust
Confidence Score
Show how sure the model is about a claim
- Trust
Verification Next Steps
Concrete actions to validate uncertain output
- Trust
Knowledge Graph
Visualizing RAG
- Trust
Citations
Attach verifiable sources to generated claims