OAuth Consent Screen
An interactive interface in the OAuth authorization code flow that shows the user the requesting application, its origin and the permission scopes, and lets the user decide whether to grant authorization.
Timeline (last 90 days)
Under Vercel's CIMD model, the OAuth consent screen displays each client's origin information: name, logo, and the hostname providing the metadata document; for example, it might show "Claude Code by claude.ai".
The "Internal" user type of the OAuth consent screen is limited to accounts within the same Google Workspace organization and does not require Google verification; the "External" user type is open to any Google account and remains in "Testing" status until published as "Production," with limits on the number of test users and token validity period.
When the OAuth consent screen is in "Testing" status, only email addresses on the test user list can complete authorization, and other accounts see an "Access blocked" error page.
When the OAuth consent screen is in testing status, the test user limit is 100.
To let any user use an OAuth application, the consent screen must be published to "Production" status; if sensitive scopes such as Gmail are requested, Google's OAuth verification process must also be passed, including privacy policy and domain verification.
All Facts (5)
Under Vercel's CIMD model, the OAuth consent screen displays each client's origin information: name, logo, and the hostname providing the metadata document; for example, it might show "Claude Code by claude.ai".
50%UnverifiedThe "Internal" user type of the OAuth consent screen is limited to accounts within the same Google Workspace organization and does not require Google verification; the "External" user type is open to any Google account and remains in "Testing" status until published as "Production," with limits on the number of test users and token validity period.
50%UnverifiedWhen the OAuth consent screen is in "Testing" status, only email addresses on the test user list can complete authorization, and other accounts see an "Access blocked" error page.
50%UnverifiedWhen the OAuth consent screen is in testing status, the test user limit is 100.
50%UnverifiedTo let any user use an OAuth application, the consent screen must be published to "Production" status; if sensitive scopes such as Gmail are requested, Google's OAuth verification process must also be passed, including privacy policy and domain verification.
50%