Role-based access control (RBAC) is a way of managing permissions where people get access based on their job role rather than one by one.
Systems · Reviewed by Ray Rasouli
Ask about role-based access control (RBAC)
Plain answers, with your setup in mind.
Ask anything about role-based access control (RBAC). For example, how it works in your current tools.
A scripted guide for now. It does not store what you type.
Instead of setting permissions for each person, you define roles such as buyer, warehouse lead or accounts payable clerk, decide what each role can see and do, and then assign people to roles.
At a distributor, a buyer might create purchase orders but not approve payments, while the controller can approve payments but not change vendor bank details. That split protects the business from honest mistakes and from fraud.
When someone changes jobs, you swap their role instead of hunting through every screen to adjust settings.
In practice
Too many roles, each slightly different.
Making a custom role for every person defeats the purpose and becomes impossible to review.
Everyone ends up as an admin.
Giving full access to fix a blocker today leaves dangerous permissions in place for years.
Roles are never reviewed.
People who changed jobs keep their old access on top of the new one.
Duties are not separated.
One role can both create a vendor and pay it, which removes a basic control against fraud.
It means giving each role only the access it needs to do the job, and nothing more. RBAC is a common way to put it into practice.
Many businesses review access at least once or twice a year, and always when someone changes jobs or leaves.
A 30-minute discovery call with Ray, then a clear list of what to fix first. No obligation.
With Ray Rasouli. No obligation.