https://foxauth.dev/docs/get-started/first-admin/ https://foxauth.dev/screenshots/admin-projects.png What a signed-in administrator lands on: the projects of the group the scope switcher is pointed at. https://foxauth.dev/docs/get-started/first-client/ https://foxauth.dev/screenshots/admin-project-clients.png A project's clients: the generated client id, the application type and the token endpoint auth method that decides whether it has a secret. https://foxauth.dev/docs/get-started/first-token/ https://foxauth.dev/screenshots/sign-in.png The sign-in screen, served for the bucket the client's project points at. https://foxauth.dev/screenshots/consent.png The consent screen lists what was asked for. `offline_access` appears only when the request also carries `prompt=consent`. https://foxauth.dev/features/ https://foxauth.dev/screenshots/admin-audit-trail.png The audit trail. Entries are written before the mutation and the store exposes no update or delete, so an entry cannot be altered after the fact. https://foxauth.dev/screenshots/admin-settings-grants.png Settings, one pane per domain. A flag here is the same key the Reference documents; changes are validated as a whole configuration before they are saved. https://foxauth.dev/ https://foxauth.dev/screenshots/admin-project-clients.png A project's clients in the built-in console. Every change here is an audit entry.