Files
classroomio/apps/dashboard/AUTH_FLOW.md
T
Rotimi Best a3924100dd feat: migrate auth from supabase to better auth (#596)
* feat: add README for @cio/db package and remove existingAccounts.json

* load session, load profile and organization, add create profile hook

* chore: cache session request

The trick was passing all the cookies to the backend. Previously I was only passing the better-auth.session_token and not better-auth.session_data. Read about the difference here https://www.better-auth.com/docs/concepts/cookies#custom-cookies

* feat: login, logout, onboarding, verify email, reset password.

* feat: complete change email and email verification

* feat: standardise how we make rpc calls and create org endpoints

* fix ui errors

* fix: handle potential undefined customerId and standardize avatar URL property

* refactor: standardize custom domain handling and update telegram chat ID references

* chore: add tailwind prefix to @cio/ui

this fixed the media query issues because  @cio/ui classes were overriding this dashboard tailwind build

* chore: clean up org sidebar

* chore: persist mode state

* feat: implement order breadcrumbs

* chore: upgrade to better auth 1.4

* chore: address common auth flow bugs and setup app for others to setup locally.
2025-11-24 01:00:50 +01:00

1.9 KiB

Auth flow

Documenting my thoughts on how authentication works in the app.

Simplified breakdown

dashboard (app.classroomio.com)

  • sign up (email, password or google auth)
  • redirect to onboarding.
  • redirect to dashboard

dashboard - invite (admin or teacher)

  • insert email into organizationmember table
  • click invite link
  • sign up or login
  • update org with role (as role in invite)

lms (school.classroomio.com)

  • create email and password
  • join org as student (automatically).

lms - invite

  • click invite link
  • redirect to login and come back to invite page.
  • join org as student (automatically).

Better Auth to Supabase TODO

actions to trigger [in code]

  • After sign up
    • create a profile by new user.
    • if sign up was triggered from a subdomain (aka is lms), add profile to org with student role
    • send verification email

migrate from supabase

  • after login redirect to next page
  • after signup redirect to next page (onboarding | lms | )
  • implement logout
  • forgot password flow
  • complete onboarding flow
  • change email flow.
  • google auth flow (local and on test environment)
  • support google auth for teacher invite
  • support google auth for student invite

others

  • block org routes when isOrgSite === true.
  • routes belonging to orgsite should proxy to courseapp (site-theme)

invite v2.0

should an admin invite student into an org alone?

  • yes
  • and also give them access to all resources in the org.

student

  • send you invite to join course
  • you click link in email
  • you are redirected to accept page
  • you enter your name and password with email prefilled
  • you click join.

how do teachers send invite?

  • email input field
  • teacher can send to multiple emails
  • teacher can deactivate access.
  • teacher can see who has accepted the invite and when.