What is a CRM role?
A role bundles the permissions a job needs into one named unit you can assign to people.
It is the mechanism that makes access manageable: change the role, and everyone in it updates, instead of editing users one by one.
Short answer
A CRM role is a named set of permissions assigned to users based on their job - defining what records, fields, and actions someone in that role can access. Roles like sales rep, manager, and admin let you manage access consistently by assigning people to roles rather than configuring each user. Roles are the backbone of role-based access control.
Key takeaways
- A named permission set assigned by job.
- Defines the records, fields, and actions a user can access.
- Common roles: rep, manager, admin.
- The backbone of role-based access control.
Why it matters
Roles make access consistent and maintainable. Everyone with the same job has the same access, and updating a role changes all its users at once. This scales cleanly as the team grows, unlike configuring permissions per individual, which drifts into an unmanageable mess.
How Ardovo handles it
Ardovo provides sensible roles out of the box with least-privilege defaults, and lets you tune them to your org. Rook flags access that deviates from a role's norm, so roles stay clean and access matches each job as the team changes.
Frequently asked questions
What is the difference between a role and a permission?
A permission is a single access right - view a record, edit a field, export data. A role is a named bundle of permissions assigned to users by job. Permissions are the building blocks; roles group them so you manage access by job rather than granting individual permissions one by one.
Why assign access by role?
Because it is consistent and maintainable. Everyone with the same job gets identical access, and updating a role changes all its users at once. Configuring permissions per individual drifts into inconsistency and becomes unmanageable as the team grows, while roles scale cleanly.
Can a user have more than one role?
Depending on the CRM, yes - some systems let a user hold multiple roles and inherit the combined permissions, useful for people who span functions. Others assign one role per user. Either way, the principle holds: access is granted through roles rather than configured per individual.