Glossary
RBAC
Definition
Role-based access control assigns permissions through job or task roles instead of configuring each account separately.
RBAC means role-based access control. Accounts receive permissions through defined roles, such as finance reader or project administrator.
A customer may include “RBAC” in a supplier security questionnaire or spreadsheet. They want to understand whether this topic affects the service you provide and what safeguards or evidence support your answer.
Role-based access control (RBAC) groups permissions into roles and assigns those roles to accounts. A role describes a set of permitted tasks, such as processing invoices or managing customer support. Several employees can share the same role while keeping individual sign-in accounts.
Roles simplify access administration when people perform similar work. Instead of rebuilding a list of permissions for every new starter, the business assigns an appropriate role. Access still needs a defined scope: permission to manage one project need not extend to every project or the entire application.
A hypothetical wholesaler might have separate roles for warehouse staff, sales and finance. Moving someone from sales to finance should trigger a review of the old role, not simply the addition of another. Otherwise, access grows with each job change.
RBAC depends on well-designed roles. A catch-all role with administrator powers defeats its purpose, while hundreds of narrowly tailored roles become hard to maintain. Check which permissions each role includes and who may change it. An application advertising RBAC can still offer roles too broad for your business.