# Delegated Consent Reduces Burden by Moving Visibility Upstream ## Claim Delegating agent authorization decisions to an identity provider reduces consent fatigue by moving both decision work and user visibility into centralized policy. <!-- atomicity: 1 idea ✓ --> ## Scope & conditions - Applies when nested agents, MCP servers, and scopes would generate repeated consent prompts. - Central policy needs inspectable grants, accountable sponsors, revocation, and action history. - Fewer prompts are not automatically better consent if users cannot see or challenge delegated authority. ## Evidence [[3. Resources/Readwise/Articles/Navigating the Identity Abyss in the AI‑Native Era - Yuichi Nakamura, Hitachi]] presents identity-provider delegation as the answer to combinatorial consent decisions while leaving the corresponding loss of user visibility mostly unexamined. ## Links - [[Default-On AI Activation Inflates Adoption Metrics at the Cost of Consent]] — contrasts: centralized authorization must not become invisible default activation. - [[Bounded Action Spaces Not Better Models Make Agents Safe to Run]] — supports: delegated policy should constrain scopes rather than rely on agent judgment. - [[An Audit Trail Is Trustworthy Only When It Is a By-Product of the Work]] — applies-in: delegated grants need observable action receipts. - [[3. Resources/MOCs/AI Agent Safety MOC]] — applies-in: the MOC lists this note under Synthesis additions (2026-08-11 — delegated consent).