Permissions

Permissions determine which pages, records, reports, integrations, and actions a user can access.

Team assignments determine which team-owned records the user can see. A user generally needs both the right permission and the right team access.

Permission categories

Permissions are grouped by category. Each permission can be enabled or disabled individually, and the All toggle enables or disables every permission in that category.

Common categories include:

  • Loads and dispatch actions.
  • Customers and carriers.
  • Billing, invoicing, ACH, Nacha, settlements, and pay holds.
  • Reports, including revenue, load, aging, cash flow, commission, and audit reports.
  • Settings, users, organization details, payment terms, and subscription billing.
  • Integrations and optional modules such as EDI, carrier onboarding providers, accounting sync, and tracking.
  • Status changes, overrides, and administrative actions.

Some permission categories appear only when the related module is available to the organization.

Review workflow

  1. Open Settings.
  2. Go to Users.
  3. Select the user.
  4. Review User permissions.
  5. Expand the relevant category.
  6. Enable or disable the needed access.
  7. Save permissions.
  8. Ask the user to sign out and back in if the change does not appear.

Missing access

If a user cannot see a page, tab, button, report, integration, EDI tender, settlement action, or QuickBooks sync option:

  1. Confirm the user is in the correct organization.
  2. Check the user's permission categories.
  3. Check the user's team assignments and default team.
  4. Confirm the related module is available to the organization.
  5. Compare access with another user in the same role and team.
  6. Have the user sign out and back in.

Best practices

Give users the access needed for their role and teams, then add elevated access only when required. Review admin, billing, settlement, ACH/Nacha, commission, integration, settings, and team-management permissions regularly.

Audit permissions should be assigned carefully. General audit timeline access, security audit events, diagnostic details, and audit exports may be separate permissions.