Skip to content

Protect & Improve

Everyone sees what their role needs. Every change leaves a trail.

Role-based access, permissions owners can delegate with a recorded history, private suspension and termination reasons, driver acknowledgements, and scheduling rules that hold the line on hours.

What's inside

Settings → Permissions

Who can do what at this station

  • Roles
  • Permissions
  • History
Owners and managers
Full access, grant permissions
Admins and dispatchers
Day-to-day operations
Drivers
Their own schedule, route and records
History
Every grant and removal, with who and when

The problem

Shared logins mean everyone sees everything.

When the team shares one login and a spreadsheet, a dispatcher can read a termination reason and anyone can quietly change last week's hours. When a decision is questioned, nobody can show who changed what.

How FLO solves it

FLO gives each role its own view, lets owners grant extra permissions one at a time with a recorded history, and keeps sensitive reasons visible to managers only.

Inside Permissions & Compliance

What it does, in detail.

Role-based access

Owners, operations managers, admins, dispatchers and drivers each see what their job needs, and each company's data is kept separate.

Delegable permissions

Owners and operations managers switch an action on for every dispatcher or admin at once, or grant it to one person: deleting a timesheet row, approving time off, suspending drivers, recognition criteria and more.

Audit history

Every permission granted or removed is recorded with who did it and when.

Suspend and terminate

Suspend a driver for set dates, terminate or reinstate them. FLO takes them off the schedule and lists the shifts that need coverage.

Private reasons

Suspension and termination reasons are visible to owners and managers, not dispatchers.

Driver acknowledgements

Drivers acknowledge shifts, announcements and coaching plans in the portal, and you can see who hasn't.

Hours rules

A seventh consecutive day is blocked and hours past 40 are flagged while the schedule is built.

Named sign-offs

Each End of Day report records who signed it off and when.

How it works

Four steps, every time.

01

Set roles

Invite your team with the role that fits each job.

02

Grant extras

Switch an action on for a whole role, or give one person extra access.

03

Act

Suspend, terminate or reinstate drivers with the reason kept private.

04

Review

Check the history whenever a question comes up.

The specifics

The details your team will ask about.

Recorded

  • Permission grants and removals
  • Suspensions, terminations and reinstatements
  • Acknowledgements, version by version
  • End of Day sign-offs

What FLO enforces

  • No seventh consecutive day
  • No assignments to suspended or terminated drivers
  • Access checked by the database, not just hidden on screen
  • Each company's records kept apart

What your team decides

  • Who gets which role
  • Who gets extra permissions
  • When to suspend, terminate or reinstate

Plan availability: Included on every plan: Starter, Fleet, Pro and Enterprise. See pricing

Who it helps

Built for everyone at the station.

DSP Owners

Control over who can see and change what.

Operations Managers

Delegate work without handing over the keys.

Dispatchers

The tools for the day, without sensitive HR detail.

HR / Admin

A record you can show when a decision is questioned.

FAQ

Questions about Permissions & Compliance.

All FAQs
  • No. Suspension and termination reasons are visible to owners and managers only. Dispatchers see that a driver can't be scheduled, not why.

See Permissions & Compliance with your own station.

Book a walkthrough with our team, or see plans and how the free trial works.

15-day free trial · Independent software, not affiliated with Amazon