Key concepts include:

Understanding how these permissions interact is critical for properly configuring user access, troubleshooting login issues, and maintaining operational security.

Create roles for your entire company for quick and easy permission granting.

1. To set the global permissions for the role, click 'Permission'.

2. For office staff, click select 'Office', make sure 'Activate Office Login' is toggled ON.

3. For drivers, select 'Road', make sure 'Activate Road Login' is toggled ON.
​

4. Once permissions have been customized, click the blue [Save] button on the bottom right corner of the screen.

This guide explains how user permission levels work throughout the platform, including expected behavior for each permission level and known exceptions discovered during testing.

The platform uses four primary permission levels:

Users with View access are expected to:

Users with View access should not normally be able to:

Users with Edit access are expected to:

Users with Edit access should not normally be able to:

Users with Full access are expected to:

Some settings may not be accessible unless the Customer Manager permission is enabled with at least View access on the related Service Category.

The Reset Password permission must be enabled for users to reset their own passwords.

If this permission is disabled:

Setting a user permission to None may generate an error message. During testing, this error did not appear to cause functional issues.

The following behaviors were observed during testing where actual system behavior differed from expected behavior.

Users with only View access to Permits were still able to:

This behavior exceeds normal View-level permissions and should be reviewed.

Users with Edit access could not:

Users with Edit access were able to:

This behavior exceeds expected Edit-level permissions.

Users with Edit access were able to:

This behavior exceeds expected Edit-level permissions.

Users with Edit access could not:

Users with Edit access could not:

Users with Edit access could not:

Users with Edit access could not:

Even with Full access, the following restrictions were observed.

Users with Full access could not:

Users with Full access could not:

Users with Full access could not:

Users with Full access could not:

Testing showed that:

This may indicate:

Users with Edit access could not:

Users with only View access to Invoice Groups were still able to:

These capabilities exceed expected View-level access.

Users with only View access to Payment Groups were still able to:

These capabilities exceed expected View-level access.

Users with only View access to Work Order Review were still able to:

Users with only View access to Invoices were still able to:

These actions typically require Edit or Full access.

Hauler Hero permissions are designed around role-based access control with optional per-user overrides. This system allows companies to create standardized roles while still supporting individual exceptions when needed.

This article explains:

Hauler Hero permissions work across three layers:

All three layers are aligned, meaning the permissions users see in the UI directly map to backend permission checks.

Permissions are primarily managed through Roles.

A role is a reusable permission template assigned to one or more users.

Examples include:

Roles are created once at the company level and then assigned to users as needed.

Navigate to:

Account Settings → Users → Roles

After assigning a role, administrators can optionally override permissions for a specific user.

This is done by enabling:

Change Individual Permissions

on the user's Profile tab.

This allows administrators to:

Navigate to:

Account Settings → Users → People

Hauler Hero supports two separate login environments:

Each role can independently allow one or both.

OFFICE_PERMISSION = 100

Office access allows users into the Hauler Hero website, including:

Typical Office users include:

ROAD_PERMISSION = 101

Road access allows users into the Driver mobile app on Android tablets.

Typical Road users include:

A common issue occurs when a driver attempts to log into the website instead of the Road app.

The error usually appears as:

Permission Denied for → read, 101

This means the user has:

The user can log into the mobile app but not the website.

Each permission category uses a four-level access ladder.

Internally, permissions use numeric values.

Some frontend areas still reference older constants:

Although the values differ, the permission behavior is the same.

The backend source of truth comes from the UserFeature.java enum.

Below are the primary permission categories currently used throughout Hauler Hero.

Controls access to business configuration settings.

Typical abilities include:

Controls the ability to manage roles and permissions themselves.

Typical abilities include:

Controls user management access.

Typical abilities include:

Users generally must have at least:

Otherwise they may encounter:

Permission Denied 101

even if other related permissions are enabled.

Controls password reset functionality.

Typical abilities include:

Controls access to the Billing module.

Controls customer-specific billing setup.

Typical abilities include:

Controls invoice access.

Typical abilities include:

Controls posting payments against invoices.

Controls overall payment management.

Typical abilities include:

Controls applying payments to specific invoices.

Controls accounting lock periods.

Typical abilities include:

Controls pricing rule management.

Typical abilities include:

Controls per-service pricing at the customer level.

Controls service definition management.

Typical abilities include:

Controls access to customer management.

Typical abilities include:

Controls route and dispatch functionality.

This is the primary operational surface used by dispatch teams.

Typical abilities include:

The Road App has its own permission structure separate from Office permissions.

Permissions are organized into three areas:

Display permissions control what information drivers can see inside the mobile app.

Examples include:

These are generally toggle-based settings.

Data Capture permissions define how drivers interact with operational events.

Each event type can be configured with one of four behaviors:

Current event types include:

The mobile app also supports additional permission categories using:

for the following areas:

Below are common permission setups observed across customer environments.

Typical configuration:

Used for:

Typical configuration:

Dispatchers often handle:

Example:
At one customer tenant, a dispatcher named Brandon handles approximately 90% of incoming calls and dispatch operations.

Typical configuration:

Controllers commonly manage:

Example configuration observed at Patriot Management:

This role is commonly used for front-office administrative staff.

Typical configuration:

Admins can generally: