User Onboarding

Users can join your company through self-registration or admin creation. This page explains both flows in detail.

Self-Registration

The most common way users join is by signing up with their company email.

Prerequisites

For self-registration to work:

1. Verified Domain — Your email domain (e.g., acme.com) must be in the company's verified domains
2. Active Company — The company must be active (not deactivated or deleted)
3. Valid Email — The user's email must be at the verified domain

Email Signup Flow

1. User visits signup page

   • Enters their company email (e.g., jane@acme.com)
   • Creates a password
   • Provides their name

2. Domain matching

   • Rahal extracts the domain (acme.com)
   • Searches for a company with this verified domain
   • If found, proceeds; if not, registration fails

3. Account creation

   • User record created with provided details
   • CompanyUser membership created
   • MEMBER role assigned by default

4. Activation

   • If allowAutoSignup: true: User is immediately active
   • If allowAutoSignup: false: User is created as inactive

5. Email verification

   • Verification email sent
   • User clicks link to confirm email
   • Account marked as verified

OAuth Signup Flow

Users can also join via Google or Microsoft login:

1. User clicks OAuth button

   • Google or Microsoft login flow
   • Rahal receives verified email from provider

2. Domain matching

   • Same as email signup
   • Domain extracted and matched

3. Account creation

   • User record created with OAuth details
   • CompanyUser membership created
   • Email automatically verified (OAuth provider verified it)

4. Activation

   • Same auto-signup rules apply

Admin-Created Users

Administrators can create users directly from the dashboard.

When to Use

• New employees who haven't self-registered
• Users who need immediate access
• Testing or demo accounts
• Users with non-standard email domains

Admin Creation Flow

1. Admin opens Create User form

   • From Users page, click "Create User"

2. Admin enters user details

   • Full name
   • Email address
   • Password
   • Phone (optional)
   • Company (required)
   • Role (required)
   • Status (Active/Inactive)

3. User created

   • User record created with provided details
   • CompanyUser membership created
   • Email marked as verified (admin-created)
   • Selected role assigned

4. User can login

   • No email verification needed
   • User logs in with provided credentials

Advantages of Admin Creation

Default Role Assignment

Self-Registered Users

All self-registered users receive the Member role:

• Basic booking permissions
• Manage own travelers
• Submit booking requests

To upgrade a self-registered user:

1. Find them in the Users list
2. Click Edit
3. Select a different role
4. Save changes

Admin-Created Users

Admins select the role during creation:

• Choose any active role
• Predefined or custom roles available
• Role takes effect immediately

Pending Users (Auto-Signup Disabled)

When auto-signup is disabled, self-registered users are created as inactive.

Identifying Pending Users

1. Go to Users
2. Filter by Status: Inactive
3. Look for recently created users

Approving Pending Users

1. Edit the inactive user
2. Change Status to Active
3. Optionally upgrade their role
4. Save changes

The user can now log in.

Rejecting Pending Users

If a user should not have access:

1. Leave them inactive, or
2. Delete them from the system

Troubleshooting Onboarding

"No company found for this domain"

The email domain isn't associated with any company:

• Check the company's verified domains
• Add the domain if it should be included
• Verify spelling (exact match required)

User created but can't login

• Check if user is inactive (auto-signup disabled)
• Activate the user from the dashboard
• Verify email verification was completed (for email signup)

OAuth user can't access

• Same domain verification applies
• Check company is active
• Verify auto-signup setting

Wrong role assigned

For self-registered users:

• Edit the user
• Change to appropriate role
• Save changes