Consent screen

A provider interface that presents an application's identity, requested access, and related terms before an account grants authorization.

OAuth and other authorization flows can show scopes on first grant, after a scope increase, during reauthorization, or under administrator policy. The screen may summarize or group permissions and does not necessarily expose every downstream use. Existing sessions, service accounts, delegated administrators, or other credentials can provide access through separate paths.

Builder example

Consent is one control point, not the final security boundary. Applications should request least privilege, explain purpose and retention, enforce permissions at runtime, offer revocation, and avoid treating a click as unlimited future consent for unrelated processing.

Common confusion: A consent screen reports the provider's authorization request; it does not prove the application will use data only as expected, and users may not be able to approve scopes individually.