TranslogiX uses BetterAuth for authentication. Users sign in with an email address and password. Sessions are stored as cookies, last seven days, and are automatically refreshed daily. This page explains the sign-in flow, session behaviour, and how roles control access to different parts of the dashboard.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/fatelessdev/translogiX/llms.txt
Use this file to discover all available pages before exploring further.
Signing in
Navigate to the login page
Open
/login in your browser. If you try to access a protected route without a valid session, TranslogiX redirects you to /login automatically.If your credentials are incorrect, the login page displays “Invalid credentials” and stays on
/login. No account lockout is applied after a fixed number of attempts.Sessions
| Setting | Value |
|---|---|
| Session lifetime | 7 days from the time of sign-in |
| Session refresh | Refreshed automatically if the session is used within the last 1 day of the current window |
| Cookie name | better-auth.session_token |
| Storage | PostgreSQL sessions table via BetterAuth |
nextCookies plugin. The cookie is set on the server and is not accessible to JavaScript running in the browser.
Roles
Every user account has exactly one role. The role determines which dashboard the user sees and which API actions they can perform.| Role | Description |
|---|---|
ADMIN | Full access to all data, users, transporters, vehicles, routes, shipments, and the AI Ops dashboard. |
TRANSPORTER | Access scoped to their own transporter organisation — vehicles, routes, and shipments. |
DRIVER | Access to driver-specific views and shipment updates. |
CUSTOMER | Access to shipment tracking for their own packages. |
Default role
New users are assigned theCUSTOMER role by default. An administrator must update the user’s role through the admin panel to grant elevated access.
Role assignment
Only administrators can change a user’s role. Roles are assigned through the user management section of the admin dashboard, not through self-service.Failed authentication
If a request reaches a protected API route without a valid session, the server returns a401 Unauthorized response. If a valid session exists but the user’s role does not permit the action, the server returns 403 Forbidden. In both cases, the application redirects the browser back to /login.