Accounts and organizations
Customer Portal users have one account and can belong to multiple organizations. Most authenticated work happens inside one active organization, which determines the data and feature permissions for each request.
Create or access an account
The configured registration mode determines the available path:
| Mode | What a visitor can do |
|---|---|
open | Create an account from /signup |
invitation-only | Register only through an organization invitation |
disabled | Sign in to an existing account; public registration is unavailable |
Email/password registration requires a name, email address, and password of at least eight characters. After registration, /verify-email asks for the six-digit one-time code sent to the email address, then returns you to /login. A password login for an unverified address sends a new sign-in code and returns to the intended route after verification.
GitHub and Google buttons appear on /login only when their providers are enabled by the deployment. A successful sign-in normally opens /dashboard or the protected route that originally sent you to the login page.
Use /forgot-password to request a reset code and choose a new password. The reset form requires the code and matching passwords.
Accept an invitation
Open the invitation link using the email address to which it was sent.
- If you need an account, registration preserves the invitation while email verification is completed. Sign in afterward to accept it automatically.
- If you are already signed in with the invited address, Customer Portal accepts the invitation and opens the dashboard.
- If the signed-in email does not match the invitation, sign out and use the invited address.
An invitation grants an organization role; it does not grant system-administrator access.
Switch the active organization
Open My organizations at /my-organizations. Each membership shows its role and whether it is active. Choose Set active on another organization before opening its dashboard or feature pages.
Understand roles
| Role | Scope | Typical responsibility |
|---|---|---|
| Owner | One organization | Full organization control and membership governance |
| Admin | One organization | Organization configuration and feature administration |
| Member | One organization | Everyday work allowed by each feature policy |
| System administrator | Entire portal | Manage portal users and organizations |
System administrators are configured separately through ADMIN_EMAILS. Organization owners and administrators do not automatically become system administrators.
If you hold that installation-wide role, use Administer the portal for user, session, and cross-organization operations.
Manage profile and organization
Open /settings to update your name, email address, and profile image. Use /settings/security to change the account password.
The /settings/notifications screen is currently a non-persistent interface preview. Its switches do not save notification preferences or establish a delivery guarantee; do not rely on them for operational alerts.
At /settings/organization, authorized owners and administrators can review organization details, members, and invitations. The controls shown there depend on the active organization and Better Auth organization permissions.
Continue with the dashboard to understand the work shown for your role, timesheet workspace setup if you administer the production module, or record a week if the workspace is ready.