FAQ overview
The FAQ is split into four categories (account and security, sign-in and verification, authorization and permissions, integration and debugging), plus the lookup order by symptom, error code and field.
The FAQ collects questions that have already been asked: confusion from end users on the consent page, and blockers developers hit while debugging. It is not systematic — it aims to be "follow this and it is solved".
This page explains the categories and the lookup order.
Categories
| Category | Answers | For |
|---|---|---|
| Account and security | Passwords and recovery, verification methods, sessions, someone else using your account | End users |
| Sign-in and verification | Why you are asked to sign in again, why you are asked to verify once more | End users |
| Authorization and permissions | What the consent page asks, what happens after revoking, scopes and audiences | End users, developers |
| Integration and debugging | Registering a client, redirect URIs, code exchange, token validation | Developers |
The split follows "whose problem it is", not "which page it is on": problems with the account's own state go to account and security, problems in the sign-in step to sign-in and verification, authorization between you and an application to authorization and permissions, and developer-side debugging to integration and debugging.
How to look things up
Try in this order, each more specific than the last:
- By symptom: what you see (no consent page, 404 on the callback, 401 from a token) maps to an entry directly;
- By error code: Error codes gives the investigation order, the FAQ gives the conclusion;
- By field: API reference gives parameters and constraints.
How it differs from the error code page
| Page | Answers |
|---|---|
| Error codes | What the determination rule for this code is, and in what order to investigate |
| FAQ | What usually causes this scenario, and how to fix it |
The error code page is complete and organised by protocol; the FAQ is empirical and organised by scenario. Where they disagree, the error code page wins.
Nothing found
Report it as "the docs are wrong" instead of working around it: a workaround leaves a long-term hazard, a wrong doc gets fixed. For how doc changes and feedback work, see the documentation outline.