Skip to content

Authentication, Onboarding, And Legal

Last audited: 2026-05-28.

Current Screens

Auth group:

  • /auth/sign-in
  • /auth/sign-up
  • /auth/forgot-password
  • /auth/invitation-code
  • /auth/terms-of-service
  • /auth/privacy-policy
  • /auth/support

Authenticated gates:

  • /role-assign
  • /legal-accept
  • /onboarding
  • /invitations/accept/[code]
  • /invitations/enter-code

Root and OAuth routes:

  • /
  • /callback
  • /logout

Current Behavior

The root route sends authenticated users to the dashboard and unauthenticated users to sign-in. The callback route completes hosted-auth/OAuth return handling and then redirects to the base dashboard route. Logout clears session state and returns to sign-in.

The auth layout redirects authenticated users away from auth screens. If an invitation is pending, the user is sent to the invitation acceptance route instead of the dashboard.

Onboarding and role assignment are separate authenticated gates. Legal acceptance uses backend legal documents and posts acceptance before allowing normal app flow.

Current Backend Touchpoints

  • GET /v1/users/current
  • POST /v1/users/init
  • GET /v1/legal/terms-of-service
  • GET /v1/legal/privacy-policy
  • POST /v1/legal/accept
  • POST /v1/invitations/{code}/accept

What To Check

  • Cognito hosted-auth/client configuration if sign-in or sign-up redirects fail.
  • Pending invitation state if users land on invitation flow unexpectedly.
  • User role and legal acceptance fields if an authenticated user loops between gates.
  • New Relic mobile breadcrumbs for auth workflow events and route changes.