Lx EdgeDocs

Organization Auth

Purpose: Explain tenant authentication flows and related pages for organization users.

Version: 0.1.0 Last updated: auto

#Quick overview

  • Org auth is tenant-oriented and permission-aware after login.
  • JWT is stored in localStorage and used for subsequent requests.

#Key URLs

#Login

  1. User action: Open the login page and submit credentials.
  2. System response: On success, you’re routed to dashboard or onboarding.
  3. Notes: Inline error on invalid credentials; token persists in localStorage.

#Signup

  1. User action: Create your account with basic details.
  2. System response: Account created; you may continue to onboarding.
  3. Notes: Org policy may require an invite.

#Invite verification

  1. User action: Open your verification link.
  2. System response: Invite validated; proceed to set password if required.
  3. Notes: Expired/invalid links provide recovery guidance.

#Onboarding

  1. User action: Complete required profile/org details.
  2. System response: Grants access to org areas upon completion.
  3. Notes: Can be resumed if interrupted.

#Logout

  1. User action: Use the logout control or URL.
  2. System response: JWT removed; user redirected to login.

#Summary

  • Org auth includes login/signup/invite/verify/onboarding.
  • After login, permissions govern access and the sidebar.