Thoughtful access for transportation teams

People should see what their job needs

A transportation business has several kinds of people around the same data: owners, dispatchers, drivers, and clients. Each needs a different view. Giving everyone the same access is simple, but it exposes information that people do not need, and it makes mistakes more costly.

How the roles differ in LimOperations

Owners and dispatchers work in the company workspace, where they manage bookings, clients, drivers, and vehicles. Drivers use a mobile portal that centres on their own rides. Clients see only their own bookings. A company can also have several owners, who all have the same privileges, which suits partners who run a business together.

Never share a login

A shared login saves a few minutes of setup and costs you accountability. When two people use one account, you cannot tell who changed a booking, and you cannot remove access for one without disrupting the other. Give each person an account.

Clients get a link, then a code

Client access works differently from staff access. The company gives a client a private link, and the client then proves who they are with a one-time code sent to the email address or phone number you hold for them. A forwarded link alone is not enough to get in.

Plan for people leaving

Access should end when a role ends. Deactivate the accounts of people who leave the same day, and review who has access when responsibilities change. Doing this regularly is a small chore, and it prevents the kind of problem that is hard to explain to a client later.

When someone leaves

A dispatcher gives notice. On their last day the company removes their access, hands their open rides to a colleague, and reviews which clients they dealt with most. Because every person had their own login, there is nothing to untangle: the history shows what they did, and nothing else needs to change.

Access review

• Everyone has their own login.
• Drivers can see only their own rides.
• Clients reach their rides by link and one-time code.
• Access is removed the day a role ends.
• Review who has access every few months.