Skip to main content

Account management

alphaswarm_admin (internal) note — the internal admin BFF at manage.alpha-swarm.ai is Entra-only post the alphaswarm_admin Entra refactor (.cursor/plans/alphaswarm_admin_entra_refactor_039f2aeb.plan.md). Service identity flows through per-deployment Entra Agent Identities; see admin-agent-identity.md. Auth0 remains the customer-facing path for the public app.alpha-swarm.ai cloud frontend described below.

1) Overview​

The /auth/profile surface is the end-user account center for identity, security, session control, connected providers, and tenancy membership management. It keeps sensitive account operations in one place while delegating authentication authority to Auth0.

2) Profile tab​

The Profile tab shows display name, avatar, and provider badge. Email is read-only because the canonical identity record is managed by Auth0.

3) Security tab​

The Security tab includes:

  • PasswordChangeCard: creates an Auth0 password-change ticket URL and redirects the user through the hosted reset flow.
  • MfaFactorsCard: lists and manages MFA enrollment for TOTP, SMS, and WebAuthn factors.
  • RecentActivityCard: displays the last 10 security-relevant audit events.

4) Sessions tab​

The Sessions tab lists active sessions with browser, device, IP, approximate location, and last activity. Users can revoke individual sessions, or run a global "Sign out everywhere" action with friction confirmation.

5) Connections tab​

The Connections tab supports linking and unlinking identity providers such as Microsoft, Google, Auth0 Database, and GitHub.

5b) Integrations tab​

The Integrations tab is a separate, unified surface for connecting external trading/data integrations (brokerages, market-data vendors, OEMS) driven by the dynamic catalog at /me/integrations/catalog. OAuth integrations redirect to the provider; BYOK integrations collect API keys inline, envelope-encrypted and never round-tripped back to the browser. It is distinct from the Connections tab, which links identity-provider logins rather than external service accounts.

6) Tenancy tab​

The Tenancy tab shows memberships, supports org/workspace switching, and exposes a user-level "Leave organization" action. Admin onboarding and tenancy administration are handled in separate admin routes.

7) Notifications tab​

Notifications is a placeholder in v1 and reserved for a future v2 notification preferences model.

8) Danger Zone​

Danger Zone contains permanent account-deletion actions gated by <ConfirmFrictionDialog> typed-email confirmation.

What an admin can additionally do​

Admins can use:

What happens on the backend​

Key backend modules: