Glossary
What is RBAC?
Role-Based Access Control
Definition
RBAC — role-based access control — grants permissions to roles (such as “sales rep” or “accountant”) rather than to individuals; users inherit a role’s permissions when they are assigned to it.
Why RBAC
With hundreds of users, managing permissions person by person is impossible. With RBAC you define roles carefully; a new hire gets exactly their colleagues’ access by receiving the role, and a transfer only changes the role.
Where RBAC stops
RBAC answers “which operations?”, not “on which records?”. For a rep to see only their own customers you also need record rules (attribute-based access control, ABAC) and field-level security.
Example
The “sales rep” role can view and create leads but not delete or export them. “Sales manager” inherits from it and adds export and assignment.
RBAC in Fidar
Fidar combines RBAC with org scope, record rules, field security and amount limits — six layers in the Users & Access module.
Updated: