Glossary
Consent screen
A consent screen shows a person what an assistant may do and lets them approve or refuse the connection before any access is granted.
Updated November 12, 2026
- Also called
authorization consent
At OneLifeVibe
- The person sees a consent screen listing what the assistant may do.
Related terms
What it means
A consent screen, also called an authorization consent, is the page where a person sees what an assistant may do and approves or refuses the connection. It sits between a request for access and the grant of access. In OAuth terms, it is where the authorization server asks the resource owner to decide whether the client gets the scopes it asked for.
The screen is not a login form. Authentication answers who the person is. Consent answers what the assistant may do on that person's behalf. Keeping those steps separate matters, because a person can sign in successfully and still decline the connection.
How it works
A client starts an OAuth authorization request and includes the scopes it wants. After the person authenticates, the authorization server renders the consent screen. The screen lists the requested scopes in readable terms and offers approve and refuse actions.
On approval, the server redirects back to the client's registered redirect URI with an authorization code. The client then exchanges that code for tokens at the token endpoint. On refusal, the server redirects with an error, commonly access_denied, and no code is issued.
The granted scopes are tied to the resulting token, so a request for fewer scopes produces a narrower grant. The client should send a state value and check it on return to prevent cross-site request forgery.
How OneLifeVibe uses it
When you connect an assistant to your OneLifeVibe account, the person sees a consent screen listing what the assistant may do. They approve or refuse the connection there.
The listed permissions relate to OAuth scopes, the same unit of access used in the authorization flow. Approval lets the connection proceed with what the screen described. Refusal stops the connection from being approved.
Common mistakes
Approving without reading the scope list. The screen exists so the person can compare what was asked for with what they expect. If an assistant requests more than the task needs, refuse and connect again with a narrower request.
Treating consent as a formality after login. A successful sign-in does not grant access. The connection still needs approval, and a refusal must be handled by the client as a normal outcome rather than a crash.
Ignoring the refusal path. OAuth returns an error such as access_denied to the redirect URI, and clients should show a clear message and stop. Also check the state parameter and validate the redirect URI exactly. Do not request scopes the integration does not use.
Questions
What is the difference between a consent screen and a login page?
The login page establishes who the person is. The consent screen shows what the assistant may do and asks them to approve or refuse the connection. A person can complete sign-in and still decline.
What happens if someone refuses the connection on the consent screen?
The connection is not approved, so no authorization code is issued. In OAuth, the authorization server typically redirects back with an error such as access_denied, and the client should handle that response without retrying in a loop.
See it working. The OneLifeVibe connector and Platform API put these pieces together.
Written from the OneLifeVibe tool registry and platform configuration, and checked automatically before publishing. Something wrong? Tell us.