What is role-based access control?
RBAC is the standard way to manage access at scale: permissions attach to roles, and users get permissions by holding a role.
It replaces the unmanageable practice of setting access per person with a clean, consistent, role-driven model.
Short answer
Role-based access control (RBAC) grants permissions based on a user's role rather than to each user individually - you define what a rep, manager, or admin can access, then assign people to roles. RBAC makes permissions consistent, scalable, and easy to maintain, since access is managed at the role level and every person in a role inherits the same rights.
Key takeaways
- Grants permissions by role, not per individual user.
- Users inherit access by being assigned a role.
- Makes permissions consistent and scalable.
- Simplifies maintenance as people join and move.
Why it matters
Setting permissions per user does not scale and drifts into inconsistency as people join and move. RBAC keeps access consistent - everyone in a role has the same rights - and maintainable, since changing a role updates everyone in it at once.
How Ardovo handles it
Ardovo uses role-based access control with sensible least-privilege roles out of the box, so access matches each job consistently. Rook flags when a user's access exceeds their role's norm, keeping the model clean as the team changes.
Frequently asked questions
How does role-based access control work?
You define permission sets for roles - what a rep, manager, or admin can see and do - then assign each user a role, so they inherit that role's access. Access is managed at the role level, so every person in a role has the same consistent rights rather than individually configured ones.
Why use RBAC instead of per-user permissions?
Because per-user permissions do not scale and drift into inconsistency as people join, move, and leave. RBAC keeps access consistent - everyone in a role has identical rights - and maintainable, since updating a role's permissions changes everyone in it at once rather than one user at a time.
What are common CRM roles?
Typically sales rep (access to own and team records), manager (broader visibility and reporting), and admin (full configuration access), often with variations like read-only or restricted roles. The exact roles reflect your org structure, with each granting the access that job needs and no more.