Control center
Settings walkthrough
Settings groups profile, organization, notifications, security, API key and integration preference routes. The live account context comes from auth.me; the other settings routes are navigational surfaces and should be treated as unavailable/scaffolded unless a real save/API operation is shown.
Key routes
- Settings overview
Open the settings landing page.
- Profile
Review the profile route and account context.
- Organization
Open organization/tenant settings.
- Security
Open security and authentication settings.
- Notifications
Open notification preference routes.
- API keys
Open API key management surface.
- Integrations
Link to integration operations.
Prerequisites and seed data
- Sign in; profile/account context is loaded using the authenticated auth.me query.
- Organization settings depend on tenant context and any role checks enforced by the backend.
- Do not enter credentials, API keys or MFA recovery material into an unsupported form or issue report.
Primary workflows
Check account context
Use the profile page to verify who is signed in and which tenant is active.
- Open settings overview. Settings overview
- Open profile and check the displayed account context. Profile
Review security surfaces
Inspect security and key-management routes without assuming an unsupported save action works.
Navigate organization and integration settings
Distinguish account settings from tenant-wide and connector operations.
- Open organization settings and verify tenant scope and role access. Organization
- Use integration navigation for connector operations; the settings link itself does not configure credentials. Integrations
Concepts
- Account context
- The current user’s identity, role and tenant returned by auth.me.
- Tenant preference
- A setting that applies to an organization/tenant rather than only one user; require tenant-admin authority.
- Credential
- A secret such as an API key or token; only manage through a working, approved secure operation.
Data sources and implementation status
- The settings route components query trpc.auth.me for authenticated identity/tenant context.
- Profile updates, notification preferences, password/MFA/session management, API-key management and integration credentials are not confirmed as wired by these routes.
- Authentication router registration and middleware are in backend/src/auth/ and backend/src/trpc/.
Permissions
- auth.me requires an authenticated session for account context.
- Tenant-wide changes should be restricted to authorized tenant administrators; the route group does not assert that the UI enforces each operation.
- Never share or log API keys, passwords, MFA secrets or bearer tokens.
Troubleshooting
| Symptom | Check | Where to look |
|---|---|---|
| Profile or tenant context is missing. | Verify authentication and the auth.me query result. | app/(app)/settings/ and backend/src/auth/ |
| A settings form has no effect. | The route is not evidence of a save API; check for a real mutation and report unsupported behavior as a gap. | app/(app)/settings/ |
| A settings page is forbidden. | Confirm tenant context and backend role middleware; do not infer access from a visible link. | backend/src/trpc/trpc.middleware.ts |
Where things live
- Settings route pages
- app/(app)/settings/
- Account context query
- app/(app)/settings/
- Authentication router
- backend/src/auth/
- Role and tenant context middleware
- backend/src/trpc/
Audience: mixed · Last reviewed: