Super Admin Control Center
Toggle modules, inspect template settings, monitor health, and manage users.
The admin area at /app/admin requires the admin role. Page layouts redirect non-admin users, and administrative API procedures enforce authorization separately.
Available sections
| Route | Purpose |
|---|---|
/app/admin/setup | Configure supported integrations and inspect setup status |
/app/admin/pricing | Edit the trusted pricing catalog and link provider prices |
/app/admin | Inspect counts, module state and environment/health summaries |
/app/admin/modules | Toggle feedback, public board, roadmap, changelog, docs, teams, mailing, analytics, AI and anonymous AI access |
/app/admin/settings | Set default locale, currency, mail sender, password policy and AI agent name |
/app/admin/users | Search and manage users, roles and impersonation |
/app/admin/feedback | Triage feedback, manage visibility, statuses and official responses |
Health summaries and configured-key indicators are not proof of end-to-end provider delivery. Use the supported integration test action and verify the actual workflow before relying on a live service.
Template settings save explicitly. The locale field selects from configured languages; password minimum length accepts 6–64, with separate character requirements. Anonymous AI access belongs to the Modules page.
Feedback merge search can find candidates beyond the current page and returns up to 25 matches. Refine the search if needed. Confirming a merge marks the source DECLINED and stores a response referencing the target; it does not move votes/comments or create a merge relation.
Create the first admin
After creating an account, run the existing promotion command against the intended database:
bun run admin:promote [email protected]Alternatively, set ADMIN_EMAILS before that user signs up. This is a privileged account change; ensure the command's database is the one you intend to administer. Sign in and open /app/admin afterward.
See Teams and Configuration.