RBAC deep dive: 42 permissions, 4 default roles, unlimited custom roles
A look inside how Yatram implements role-based access control for multi-tenant SaaS fleets.
Why fleet RBAC is harder than it looks
Most SaaS platforms get away with three roles: admin, user, read-only. Fleets do not work that way. A dispatcher needs to create trips but not delete them. A finance manager needs invoices but not GPS positions. A driver needs their own assignments but nobody else is.
Yatram RBAC at a glance
- 42 granular permissions like
devices.command,reports.schedule,finance.manage - 4 seeded system roles: super_admin, admin, staff, viewer
- Unlimited custom tenant-specific roles (clone-and-customise)
- Union semantics: a user with multiple roles gets the superset of grants
- Plan-tier gating: some permissions only unlock on higher tiers
Build your own role
Open cpanel → Roles & Permissions → New custom role. Pick an existing role as the starting point, tweak the grants, save. Done.