Role-Based Access Control
In Arabicالتحكم في الوصول حسب الأدوار
Giving each user only the screens, actions and vehicles their role needs, instead of full access to the fleet platform for everyone.
What is role-based access control in fleet management?
Each fleet role, such as dispatcher, branch manager or system administrator, is defined as a set of permissions and a scope of vehicles, and each user gets what matches their role. A dispatcher monitors but cannot edit alarm conditions; a branch manager sees one branch.
In Safee the company administrator sets, for each account, which levels of the fleet hierarchy it sees (Permitted Level) and its Account Permissions for Exploring and Monitoring, Management, Reports and Alarm Condition. Immobilisation has a permission of its own.
How it works
- 1Define roles and what each needs
- 2Link each account to role and scope
- 3Review accounts when duties change
Why does role-based access control matter in fleet management?
One wrong edit to an alarm condition or the fleet hierarchy changes what everyone receives and what every report says. An immobilise command in the wrong hands can stop a vehicle in the middle of a sensitive job. Tight access cuts configuration errors and misuse, and protects customer data when outside parties log in.
What you gain
- Fewer configuration mistakes
- Each branch's data protected
- Sensitive commands kept to few
How does Safee help with role-based access control?
Safee ties each account to a scope of vehicles and a set of allowed actions, so dispatchers see monitoring only, branch managers see their own branch, and immobilisation and alarm editing stay with a few people. Accounts can also expire on a set date, which suits contractors and temporary auditors.
A field example
A school-bus operator in Nizwa had 40 accounts with full rights, and a staff member accidentally edited the overspeed condition, silencing its alerts for a week. Management redrew the roles: 3 administrators for settings, dispatchers with monitoring only, a coordinator per school seeing only that school's buses, and immobilisation for two supervisors. No unintended change happened the following term.
Frequently asked questions
Can a user be limited to a single branch?
Yes. The account's vehicle scope decides what it sees, and reports, the dashboard and alarms respect it.
Why is immobilisation a separate permission?
Stopping a vehicle has a direct safety and operational impact, so it is given only to chosen accounts.
Can access be granted temporarily?
Yes. An account can be given an expiry date, after which it stops working; useful for contractors, visitors and auditors.
Want to put this to work in your fleet?
Talk to a Safee fleet expert about your vehicles and how you operate, and we will suggest what fits.
Request a consultationSafee fleet management newsletter
Fleet management news, updates and practical tips, sent to your inbox regularly.