Introduction
Once a fleet spreads across branches, the hardest part of GPS tracking isn’t the tracking. It’s deciding who gets to see and do what. Good fleet management user roles keep each branch focused on its own vehicles, give head office the full picture and make sure the right people get the right comprehensive reports without everyone seeing everything.
Picture a transport company with a head office in Ahmedabad and three branches. In the first month, everyone shares one login because it’s easy. By the third month, nobody knows who changed an alert limit. A branch manager who left in the summer still has access. And the accounts team is emailing screenshots because they can’t download the fuel report themselves.
None of this is dramatic. It’s what happens when roles are never designed. Here’s how to design them.
Why Roles Matter When You Have Branches
With one depot, “everyone sees everything” is manageable. With several, it causes real problems:
- Branch managers see vehicles that aren’t theirs, which leads to confusion and arguments about whose truck it is
- Sensitive data spreads too widely, such as driver behaviour or location history
- Settings get changed by people who shouldn’t change them, and nobody knows who did it
- Former employees keep access because nobody remembers to remove it
- Reports pass through too many hands, and different branches end up working from different versions of the numbers
Roles fix this by matching what people can see and do to what they actually need.
Three Questions Behind Every Permission
Before you create any role, ask these about each person:
- What do they need to see? Which branches, vehicles and reports?
- What do they need to change? Alert limits, zones, users, vehicle details?
- What do they need to take away? Who needs to download or share reports?
Most permission problems come from skipping the third one. Viewing a report and exporting it are not the same thing.
A Simple Role Model for Multi-Branch Fleets
Use this as a starting point and adjust it to your own organisation. These are example roles, not a list of what any particular system offers.
| Role | Typically sees | Typically can change | Reports |
| Owner or admin | All branches and vehicles | Users, roles, alert rules, settings | All, with export |
| Head office operations | All branches | Alert rules, zones | All, with export |
| Branch manager | Own branch vehicles | Acknowledge alerts, update branch zones | Branch reports, with export |
| Dispatcher or supervisor | Assigned vehicles, live map | Nothing, or assign jobs | Live status only |
| Accounts or finance | Reports only | Nothing | Fuel, distance and summary reports |
| Maintenance | Service and vehicle-health data | Service reminders | Maintenance and usage reports |
| Auditor or read-only | Selected branches | Nothing | Selected reports, view only |
The pattern is simple: the wider someone’s view, the narrower their ability to change things.
Report Access: Who Should See What
Reports are where a lot of the value, and the risk, sits. A system like Sahaj’s offers trip and route reports, alert logs, stoppage reports and daily, weekly or monthly summaries, and you can filter them by any date or time range. Here’s one way to decide who gets which.
| Report type | Useful for | Suggested access |
| Trip and route history | Operations, dispatch, dispute resolution | Branch manager, head office, dispatcher (limited) |
| Stoppage and idling reports | Spotting waiting time and halts | Branch manager, head office |
| Alert logs (overspeeding, harsh braking, idling, route deviation) | Safety and driver coaching | Branch manager, head office, HR where relevant |
| Daily, weekly and monthly summaries | Management reviews | Owner, head office, branch manager |
| Fuel and distance reports | Cost control and billing | Finance, head office, branch manager |
A few rules worth following:
- Driver behaviour data is sensitive. Share it with the people who coach drivers, not the whole company.
- Limit who can download. Viewing is lower risk than exporting, because exported files travel.
- Keep one source of truth. If branches build their own spreadsheets, you’ll spend meetings arguing about numbers.
Setting Up Branches the Way You Actually Work
The structure you choose should mirror how the business runs.
- Group vehicles by branch first. Then by vehicle type or customer if you need to.
- Use a clear naming pattern. For example, branch code, vehicle type and registration number, so the list sorts logically.
- Decide how transfers work. When a vehicle moves between branches, who updates its group, and when?
- Keep shared vehicles to a minimum. A vehicle that belongs to two branches belongs to nobody.
A tidy structure now saves a lot of cleaning up later.
Alerts: Who Gets Which Notifications
Alerts are useless if they go to the wrong person, and noisy if they go to everyone. Route them with a plan.
| Alert | Best recipient |
| Over-speeding and harsh braking | Branch manager |
| Long idling | Branch manager or dispatcher |
| Route deviation | Dispatcher, then branch manager |
| Device offline or no data | Admin or head office |
| Zone entry and exit at key locations | Dispatcher |
Sahaj’s instant alerts arrive by app, SMS or email, so you can choose how people receive them. Start with a few alerts per role and add more only when someone asks. Too many alerts and people stop reading any of them. For safety coaching, driver behaviour monitoring shows speed, braking and idling patterns, and it’s best shared with the people who run driver coaching.
Access Hygiene: The Habits That Keep It Secure
Roles only work if they’re maintained.
- One person, one login. Shared logins make it impossible to know who did what.
- Give the least access that does the job. Add more when someone needs it, not “just in case.”
- Remove access on the day someone leaves or changes role. Make it part of your exit checklist.
- Review the user list every quarter. Look for unused accounts and roles that no longer fit.
- Use strong passwords, and turn on extra verification where it’s offered.
- Give temporary access for audits, then remove it.
We’ve covered the wider security picture in our guide to the cybersecurity risks in fleet tracking systems.
Common Mistakes to Avoid
- Sharing one login across a branch or team
- Giving every branch manager head-office access “to keep things simple”
- Letting everyone export reports
- Never removing access for people who left
- Creating dozens of custom roles nobody can remember
- Routing every alert to everyone
- Letting each branch keep its own version of the numbers
A 30-Day Rollout
You don’t need a big project.
| When | What to do |
| Week 1 | List every branch, vehicle and user. Decide your roles (five or six is plenty) |
| Week 2 | Group vehicles by branch. Create the users and assign roles |
| Week 3 | Set alert routing and report access. Remove shared logins |
| Week 4 | Get feedback from branch managers, adjust, and set a quarterly review date |
What to Ask Your GPS Provider
If you’re choosing or reviewing a system, ask:
- Can we group vehicles by branch, and restrict users to their own branch?
- Can we create or customise roles?
- Can we control who can view, change and export?
- Can reports be limited by branch, vehicle or type?
- Can alerts be sent to specific users?
- Is there an activity log showing who changed what?
- How do we remove a user, and how fast does it take effect?
- Is there an API if we want data in our own systems?
For a wider look at the numbers branches should be reviewing, see our guide to essential fleet management reports, and for the multi-location picture, our post on GPS tracking for multi-city fleets.
How SAHAJ GPS Helps
SAHAJ GPS Vehicle Tracking System is built for fleets of all sizes, from a couple of vehicles to hundreds. According to the website:
- Comprehensive reporting covers trip and route history, alert logs, stoppage reports and daily, weekly or monthly summaries, with custom date and time filters
- Reports can be downloaded and shared, and viewed on web and mobile
- The platform uses encrypted servers and role-based access
- Instant alerts are sent by app, SMS or email
- A customisable API is available for integration
- Dedicated support and training are provided
One honest note: the website doesn’t detail the specific roles, branch structure or export restrictions available. For a multi-branch setup, share your branch list and the roles you’d like with the team, and ask exactly what can be configured.
Frequently Asked Questions
What are fleet management user roles?
They’re sets of permissions that decide what each user can see and do in the system, such as which vehicles, reports and settings they can access.
How should I set up user roles for multiple branches?
Group vehicles by branch, give branch managers access to their own branch, give head office a wider view and give finance and auditors report-only access.
Who should be allowed to download reports?
Only the people who need them. Viewing a report carries less risk than exporting it, so limit downloads to roles that genuinely need files.
Should drivers have access to the system?
Usually not to the full platform. If they need anything, a limited view of their own trips is enough, and what’s tracked should be explained to them.
How often should I review user access?
At least once a quarter, and immediately whenever someone leaves or changes role.
Final Thoughts
Good GPS data helps every branch. But data without roles creates noise, arguments and risk. Decide who sees what, who changes what and who takes files away, and most of the mess never starts.
If you’re planning a multi-branch setup, talk to the SAHAJ GPS team and ask what can be configured for your branches.