Role-Based Access Control (RBAC)

What is Role-Based Access Control (RBAC)?

Role-based access control (RBAC) is an access model in which permissions belong to roles such as viewer or billing admin, and users get access by being assigned to those roles. It simplifies auditing and supports least privilege.

Updated November 2026 · 3 min read


Role-based access control (RBAC) is a way of managing permissions in which access rights are assigned to roles, and people are assigned to roles, rather than permissions being granted to each person individually. A support agent role might allow viewing customer records and issuing refunds up to a limit; anyone given that role gets exactly those permissions, and changing the role changes access for everyone in it.

RBAC makes access easier to manage, audit and reason about as organizations and systems grow. It supports the principle of least privilege, meaning people get only the access their job requires, and it is a common expectation in security frameworks and audits. The model was formalized by researchers at the US National Institute of Standards and Technology (NIST) in the 1990s and later published as the ANSI/INCITS 359 standard.

Core RBAC concepts

  • Users. People or service accounts that need access.
  • Roles. Named job functions, such as viewer, editor, billing admin or support agent.
  • Permissions. Approved operations on resources, such as read invoices or delete projects.
  • Assignments. Users are assigned to roles; permissions are assigned to roles.
  • Sessions. In the formal model, a user activates some of their roles in a session.

Types of RBAC

ModelWhat it addsExample
Flat (core) RBACUsers, roles and permissions onlyViewer, editor and admin roles in a web app
Hierarchical RBACRoles inherit permissions from other rolesAdmin inherits everything an editor can do
Constrained RBACSeparation-of-duty rules that prevent conflicting rolesThe same person cannot both create and approve a payment

RBAC vs. other access control models

  • Access control lists (ACLs) attach permissions to each resource for specific users or groups. Fine-grained but hard to manage at scale.
  • Attribute-based access control (ABAC) decides access using attributes of the user, resource and context, such as department, data classification, location or time. More flexible than RBAC but harder to design and audit.
  • Relationship-based access control decides access based on relationships, such as "members of this workspace." Common in collaboration products.

Many products combine them: RBAC for broad job functions, with attributes or resource-level sharing for exceptions.

How to implement RBAC

  1. Inventory resources and actions. List what needs protecting and the operations people perform.
  2. Define roles from job functions. Start with a small number based on real responsibilities, not individuals.
  3. Map permissions to roles. Apply least privilege; grant only what each role needs.
  4. Add constraints. Define separation-of-duty rules for sensitive actions.
  5. Assign users and automate. Connect role assignment to the identity provider and HR events so joiners, movers and leavers are handled automatically.
  6. Review regularly. Run periodic access reviews and log access changes for audit. See audit trail.

An RBAC example

Consider a hypothetical SaaS company with 400 employees whose admin console grants permissions to individuals. An audit finds about 1,100 individual permission grants, including 35 belonging to people who changed teams and kept their old access.

The company defines 12 roles, such as support agent, support lead, billing specialist and engineering on-call, each with a documented permission set. A rule prevents anyone from holding both the billing specialist and refund approver roles. Role assignment now follows HR job changes, so movers lose old access automatically, and the quarterly access review checks 12 role definitions and each user's roles instead of over a thousand individual grants.

Common pitfalls

  • Role explosion. Creating a new role for every exception produces hundreds of near-duplicate roles that are as hard to manage as individual permissions.
  • Overly broad roles. A catch-all admin role given to many people defeats least privilege.
  • No process for movers. People who change jobs accumulate access unless role changes remove old roles.
  • Ignoring service accounts. Automated accounts often hold powerful permissions and are reviewed least.
  • Treating RBAC as one-time setup. Products and jobs change, so roles need regular review.

RBAC supports frameworks such as SOC 2 and ISO 27001, is often documented in an access control matrix, and forms part of a company's security architecture.

Frequently asked questions

What is the difference between RBAC and ABAC?

RBAC grants access through roles tied to job functions, such as viewer or billing admin. Attribute-based access control decides each request using attributes of the user, resource and context, such as department, data classification, location or time. ABAC is more flexible but harder to design and audit, so many products use RBAC broadly and attributes for exceptions.

How do you implement RBAC?

Inventory the resources and actions to protect, define a small set of roles from real job functions, and map least-privilege permissions to each role. Add separation-of-duty rules for sensitive actions, connect role assignment to the identity provider and HR events so joiners, movers and leavers are handled automatically, and run periodic access reviews.

What is role explosion in RBAC?

Role explosion happens when a new role is created for every exception, leaving hundreds of near-duplicate roles that are as hard to manage as individual permissions. Keep RBAC roles based on job functions, and handle genuine exceptions with attributes or resource-level sharing instead. Regular access reviews help spot roles that can be merged or retired.