Delegated access acts on behalf of a signed-in user and is bounded by that user's entitlements, while application access is direct app-to-resource access with broader organisational reach. Governance must distinguish them because delegated permissions still create durable machine access paths that require lifecycle review and revocation.
Delegated access versus application access in OAuth governance
Delegated access and application access solve different governance problems, even though both use OAuth. Delegated access is user-bound: the app acts with a signed-in person’s authority and should inherit that person’s entitlements. Application access is app-bound: the workload authenticates and operates on its own, which usually creates a wider standing access footprint that must be governed as a machine identity or service principal.
The practical difference is who owns the authority and how long it should exist. Delegated access should usually be reviewed as part of user consent, session scope, and user lifecycle. Application access should be reviewed as a persistent organisational grant, with tighter control over who can approve it, what it can reach, and how it is revoked when the app is no longer needed.
That distinction matters because OAuth permissions can look similar in logs while behaving very differently in operations. A delegated token may be short-lived, but the approved grant can still leave a durable access path through refresh tokens, consented scopes, or downstream APIs. An application grant can bypass any user present at runtime, so governance has to treat it as a direct trust relationship rather than a user convenience feature.
How to govern consent, scope, and revocation differently
Good governance starts by classifying every OAuth grant as either user-delegated or application-only before it is approved. Delegated access should be limited to the minimum user-scoped data and actions needed for the workflow, while application access should be limited by purpose, environment, and resource audience, not by the presence of a human approver.
Review should also be different. Delegated access is best governed through periodic review of consent, scope drift, and whether the user still needs the integration. Application access needs inventory discipline: which apps exist, which resources they can call, who owns them, and whether the grant still matches the business case. For broader identity governance patterns, IAM and IGA Basics gives the underlying access-review model that makes this split operational.
Revocation should also follow the access type. Removing a user’s delegated permission should invalidate the consent path and any associated tokens or sessions. Removing application access should remove the app registration, secret, certificate, or federation path that makes the workload able to authenticate at all. If you only remove one layer, the other often remains usable.
For OAuth-specific mechanics, RFC 6749: The OAuth 2.0 Authorization Framework is the base standard for understanding grant types, while RFC 8693: OAuth 2.0 Token Exchange is the right reference when delegated authority is being exchanged or downscoped between systems.
Why OAuth governance treats these grants as different trust paths
Delegated access is usually easier to reason about when the user is the control boundary. The user can sign out, lose access, or have their account disabled, and those actions should interrupt the delegated path. Application access does not depend on an interactive user, so its risk profile is closer to a service credential than to a session. The application can continue to operate after staff changes unless the organisation explicitly manages its lifecycle.
That is why application access often needs stronger guardrails than delegated access, especially when the app can reach sensitive APIs or shared data stores. The same rule applies to the consent model: user consent is not a substitute for governance over the app’s standing privileges. Where token-based delegation is used, OAuth Token Exchange and Delegation Guide is useful for understanding how on-behalf-of patterns change the trust chain without changing the need for revocation.
For teams that need a broader mental model, Human vs Non-Human Identity helps separate user-driven access from workload-driven access, which is exactly the distinction OAuth governance must preserve.
Risk and Threat Considerations
The main governance risk is assuming that delegated access is harmless because it “belongs to the user.” In practice, delegated OAuth grants can preserve durable access paths even after the user leaves, if consent is not reviewed or if refresh-token and app-grant revocation is incomplete. Application access creates a different exposure: a non-interactive app can retain broad reach, making it attractive for abuse, token theft, and lateral movement through trusted API calls.
Failure mechanism: Consent, token lifecycle, and app registration lifecycle drift apart, so a grant remains active after the original business need has ended or the user has changed roles.
Impact: Attackers or overprivileged integrations can continue to access mailboxes, files, records, or APIs through a still-valid OAuth path, often without triggering user-facing controls.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
OWASP Non-Human Identity Top 10 addresses the attack and risk surface, while NIST SP 800-53 Rev 5, CIS Controls v8 and OWASP ASVS set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | AC-2 — Account Management | OAuth grants need lifecycle review, ownership, and revocation control. |
| IA-5 — Authenticator Management | OAuth tokens, secrets, and refresh material require lifecycle governance and revocation. | |
| AC-6 — Least Privilege | Delegated and application access both require scope minimisation and bounded reach. | |
| Recommendation — Apply AC-2 to inventory, review, and remove OAuth access when business need ends. Apply IA-5 to manage OAuth credentials, token lifetimes, and revocation paths. Apply AC-6 to constrain OAuth scopes to the minimum required access. | ||
| CIS Controls v8 | CIS-5 — Account Management | OAuth apps and user-consent paths need inventory, ownership, and removal discipline. |
| Recommendation — Use CIS-5 to track, review, and remove OAuth grants and application access. | ||
| OWASP ASVS | V10 — OAuth and OIDC | The question is about OAuth governance, consent, tokens, and delegated versus app access flows. |
| Recommendation — Use V10 to validate OAuth grant handling, scope control, and token use. | ||
| OWASP Non-Human Identity Top 10 | NHI-05 — Overprivileged NHI | Application access often becomes persistent machine access with broader reach than intended. |
| NHI-07 — Long-Lived Secrets | Application access commonly depends on enduring secrets or certificates that outlive user sessions. | |
| NHI-01 — Improper Offboarding | Revocation failures leave delegated or application grants active after the original need ends. | |
| Recommendation — Review OAuth app permissions for excess privilege and remove unused scopes. Rotate or replace long-lived OAuth app secrets before they become standing access. Remove OAuth grants and app credentials when the owning user or service is offboarded. | ||
Practitioner Guidance
What to verify: Before approving or renewing any OAuth grant, verify whether the requested access is truly delegated, truly application-only, or a mix of both through token exchange or downstream service calls. That classification should drive approval authority, review frequency, and revocation procedure.
Decision rule: If the integration can act without a signed-in user, treat it as standing application access and require explicit ownership, scope review, and a clear removal path. If the integration needs a user context, treat the user consent and session as part of the control surface and validate that revocation really breaks access.
What good looks like: Every OAuth app has a named owner, a documented purpose, a least-privilege scope set, and a tested revocation process. Delegated grants are reviewed like user entitlements; application grants are reviewed like service credentials.
Practitioner takeaway: The governance mistake to avoid is merging user-bound consent and app-bound standing access into one approval model, because they fail differently and must be revoked differently.
Related resources from NHI Mgmt Group
- Guide: Customer IAM (CIAM) Guide
- How should teams account for delegated access and OAuth apps in identity governance?
- What is the difference between application access and agent identity governance?
- How should organisations prioritise GRC controls when starting application access governance?
- What is the difference between human identity controls and OAuth application governance?
Deepen Your Knowledge
Free weekly newsletter
Subscribe to the NHI & AI Identity Journal
The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.
Bonus 33% off our NHI Course when you subscribe.
Reviewed and updated by the NHIMG editorial team on November 2, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org