Authentication for HaloRT SaaS and mobile is owned by the platform API.
Methods
| Method | Notes |
|---|---|
| Magic link | Email link → verify → JWT; used heavily on mobile and web |
| Google OAuth | Web + mobile; needs production secrets on the API |
| Bearer JWT | Subsequent API calls; stored securely on mobile (e.g. EncryptedSharedPreferences on Android) |
Key routes include /api/auth/magic-link, Google auth endpoints, /api/auth/me.
Tenancy during login
Auth still needs a tenant context (slug / header / host) so membership resolves to the right community.
Transactional mail (welcome, reset, magic link, …) goes through Notifications with templates from @halort/email (Surfaces/Design System).