User Groups
Organize travelers into groups for policy targeting and streamlined approvals.
User Groups allow you to organize travelers and apply policies based on team, department, or any other criteria.
Why Use Groups?
Groups are essential for:
- Policy Targeting — Apply different travel policies to different teams
- Default Approvers — Automatically route approvals to the right manager
- Organization — Keep track of who belongs to which team
Example Use Cases
| Group | Policy Applied | Default Approver |
|---|---|---|
| Sales Team | Sales Travel Policy (higher budgets) | VP of Sales |
| Engineering | Standard Policy | Engineering Manager |
| Executives | Executive Policy (business class) | CEO/CFO |
| Contractors | Contractor Policy (economy only) | Project Manager |
Creating Groups
- Navigate to Groups
- Click Create Group
- Fill in the details:
- Group Name — A descriptive name (e.g., "Sales Team")
- Description — What this group is for (optional)
- Default Approver — Who approves trips for this group (optional)
- Click Create Group
The default approver must have either the Owner, Travel Admin, or Approver role.
Managing Group Members
Adding Members
- Find the group in the table
- Click Members
- In the "Add Members" section, click the + icon next to a user
Only active organization members can be added to groups. Pending invitations can have groups pre-assigned, but they won't appear as members until accepted.
Removing Members
- Click Members on the group row
- In the "Current Members" section, click the - icon next to a user
Removing a user from a group immediately changes which policies apply to them.
Group Invitation Codes
Generate unique codes that allow users to join groups directly through the Helix app.
Generating Invitation Codes
- Go to Groups page
- Find the group you want to create a code for
- Click to view group details
- Generate an invitation code
- Share the code with team members
Invitation codes make it easy for users to join groups without admin intervention. Users enter the code in the Helix app to join the group.
Using Invitation Codes
For Admins:
- Generate codes for groups that need easy joining
- Share codes via email, Slack, or other communication channels
- Regenerate codes periodically for security
- Track which users joined via which code
For Users:
- Enter the invitation code in the Helix app
- Automatically join the group when code is entered
- Gain access to group policies immediately
- No need to wait for admin to add them manually
Regenerating Codes
For security, you can regenerate invitation codes:
- Go to the group details
- Click Regenerate Code
- A new code is generated
- Old code becomes invalid
- Share new code with team members
When you regenerate a code, the old code stops working. Make sure to share the new code with anyone who needs it.
Tracking Code Usage
View who joined via invitation codes:
- See which users joined via which code
- Track code usage and effectiveness
- Identify which codes are most used
- Monitor group growth through codes
Default Group Assignment
You can set a default group for new users:
- New users automatically join the default group
- Useful for standard policy application
- Can be changed per user after joining
- Simplifies onboarding process
Editing Groups
To update a group's name, description, or default approver:
- Find the group in the table
- Click the pencil icon
- Make your changes
- Click Save Changes
Deleting Groups
Deleting a group removes all member associations. Users in the group may no longer have a policy applied to them.
To delete a group:
- Find the group in the table
- Click the trash icon
- Confirm the deletion
Policy Assignment
Groups are the connection between users and policies. Here's how it works:
- Create a group (e.g., "Sales Team")
- Add members to the group
- Assign a policy to the group (in the Policies page)
When a group member books travel, the system checks which policy is assigned to their group(s) and enforces those rules.
Multiple Group Memberships
Users can belong to multiple groups. If a user is in multiple groups with different policies:
- The most restrictive rules typically apply
- You can use policy priority settings to control which takes precedence
Best Practices
Naming Conventions
Use clear, consistent names:
- ✅ "Engineering - Backend Team"
- ✅ "Sales - EMEA Region"
- ❌ "Group 1"
- ❌ "John's team"
Group Structure
Consider organizing groups by:
- Department — Engineering, Sales, Marketing, HR
- Region — EMEA, APAC, Americas
- Seniority — Executives, Managers, Staff
- Project — Project Alpha, Project Beta
Approver Assignment
- Set default approvers to reduce manual approval routing
- Ensure approvers have appropriate permissions (Approver, Travel Admin, or Owner role)
- Consider backup approvers for when the primary is unavailable
Regular Maintenance
- Review group memberships quarterly
- Update groups when team structures change
- Remove inactive groups to keep the list clean