Role-Based Access Control (RBAC)
Role-based access control (RBAC) grants permissions to job roles, such as "accounts payable" or "sales", rather than to individual people. Users get access by being assigned a role, which makes permissions easier to manage and review.
Also called: RBAC, role-based security, role-based permissions
What is role-based access control?
In RBAC, permissions belong to roles, and people get permissions by being given a role. NIST developed and published the RBAC model, which later became a national standard and is now built into most business software, from Microsoft 365 to accounting and CRM systems.
How does RBAC work?
- Define roles that match real jobs: for example, "Bookkeeper", "Sales rep", "Office manager", "IT admin".
- Give each role the permissions it needs and nothing more, following least privilege.
- Assign people to roles. A new hire in sales gets the "Sales rep" role and everything that comes with it.
- Change roles, not individual permissions, when someone moves jobs, and remove all roles when they leave.
Why it helps
- Access stays consistent, so people don't collect permissions over the years.
- Reviews are simpler: check what each role can do, and who has each role.
- Onboarding and offboarding are faster and less error-prone.
- Separation of duties is easier, such as making sure the person who creates a supplier can't also approve payments to it.
Tips for small businesses
Keep roles few and broad at first, use groups in your identity provider to assign them, keep admin roles separate from everyday accounts, and review role memberships at least once a year.
Related terms
Sources
Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.
