Explore the Admin Dashboard
Explore the Admin Dashboard
Section titled “Explore the Admin Dashboard”The Seamless Auth Admin UI is the operator-facing application for managing and investigating a Seamless Auth deployment.
It runs as a separate app and uses the same auth system as the rest of your stack. In a project
scaffolded with seamless init, your API serves it at http://localhost:3000/console by default.
Access Requirements
Section titled “Access Requirements”Dashboard access is controlled by scoped admin roles.
In the current dashboard app:
- unauthenticated users are redirected to
/unauthenticated, which links to the dashboard sign-in at/login - authenticated users without admin read access are also redirected to
/unauthenticated admin,admin:read, andadmin:writecan read dashboard dataadminandadmin:writecan perform write actions- sensitive write actions require fresh step-up verification, by passkey or, when enabled, TOTP
Main Areas
Section titled “Main Areas”The current dashboard app includes:
- Overview
- Users
- Organizations
- Enrollment
- Coverage
- Sessions
- Events
- Security
- System configuration
- Profile
Enrollment shipped in dashboard v0.8.0 and Coverage in v0.9.0. The auth API image v0.17.0
serves dashboard v0.9.1 at /console, and a project scaffolded by seamless-cli 0.20.0 runs
that image (or the standalone dashboard image v0.9.1), so both screens are there. A project
scaffolded by seamless-cli 0.19.0 or earlier pins dashboard v0.7.0 and an auth API without the
routes behind them, so it has neither.
What You Can Do There
Section titled “What You Can Do There”Overview
Section titled “Overview”Use the overview screen to quickly answer:
- is the system active?
- are logins succeeding?
- are there suspicious signals worth investigating?
- how much passkey and session activity is happening?


Use the users screen and user detail view to:
- browse and search identities
- create, edit, and delete users
- update global roles
- inspect credentials
- review user sessions and anomalies
- revoke one or all user sessions
- start device replacement recovery
Device replacement recovery revokes sessions, removes passkeys, and disables TOTP credentials, and
returns counts only. It requires admin:write, fresh step-up authentication, and a record of how
you proofed the user’s identity (in person, or a remote exception with a named approver).



Organizations
Section titled “Organizations”Use the organizations screen to:
- create and delete organization records
- edit organization name and slug
- review membership counts
- add and remove members
- update organization membership roles and scopes
Organization routes are separate from global user roles. Use them when access depends on tenant or workspace context.
Enrollment
Section titled “Enrollment”Use the enrollment screen to:
- filter users by organization, passkey enrollment status, and how they were added
- invite users who still need a passkey (requires
admin:write)
Coverage
Section titled “Coverage”Use the coverage screen to:
- see how many users hold a phishing-resistant credential, overall and by organization
- review the coverage trend, authenticator mix, and sign-in mix
- check the login policy the deployment enforces
- download the report as CSV
Sessions
Section titled “Sessions”Use the sessions screen to:
- inspect active sessions
- review device/browser context
- identify stale or risky access
- revoke individual sessions
- revoke selected sessions in bulk

Events
Section titled “Events”Use the events screen to:
- inspect auth flow history
- filter event types
- debug failed or unusual behavior
- review OAuth, TOTP, session, and admin-sensitive events


Security
Section titled “Security”Use the security screen to:
- review anomaly signals
- inspect failed login pressure
- pivot into suspicious events
- support lockout-policy investigations
- verify the audit trail hash chain and export a period of events (export requires step-up)


System Configuration
Section titled “System Configuration”Use the system screen to review and update runtime auth configuration:
- app name
- default and available roles
- login methods, passkey fallback, and passkey enrollment prompts
- “Phishing-resistant only” mode (not yet in a tagged release)
- OAuth provider configuration
- access and refresh token TTLs
- rate limit and slowdown values
- account lockout policy
- WebAuthn relying party ID and allowed origins
- authenticator policy, such as synced passkeys and AAGUID allow and deny lists
OAuth provider client secrets stay in environment variables referenced by provider config. Do not paste raw provider secrets into the dashboard.


How It Connects To The Stack
Section titled “How It Connects To The Stack”The dashboard calls <API_URL>/auth/* on your application backend, and the server adapter
mounted there forwards each call to the auth API. Through the adapter, it sits on top of:
- admin routes such as
/admin/*, including admin session routes under/admin/sessions/* - internal metrics routes such as
/internal/* - system config routes such as
/system-config/* - step-up routes such as
/step-up/*
If you want the technical route map, see Auth API Routes.
When To Use This Page
Section titled “When To Use This Page”Use this page as a quick orientation guide during your first local run.
For deeper product docs, continue to: