Skip to content

Guide

CRM access control: roles vs relationships

Role-based access control (RBAC) decides what a person may do in a CRM based on their role. Relationship-based access control (ReBAC) decides which records they may see based on their relationship to each record, such as assignee, team manager or shared viewer. Sales CRMs work best with both: roles for capabilities, relationships for leads.

By the Swastik CRM team, Shwastik Tech Solutions Pvt Ltd · Published · Last reviewed

Key takeaways

  • RBAC gives permissions by role; ReBAC gives access by relationship to a record.
  • Use roles for capabilities (import, export, settings) and relationships for which leads a person sees.
  • Sales teams need own-lead, team, reporting-line and single-lead sharing patterns.
  • List queries must apply the same rules as single checks, as a database filter.
  • Make export a separate permission and keep an audit log.

What question does CRM access control answer?

“Who can see and change this lead?” It sounds simple until you list the real answers in a sales organisation: the agent it is assigned to, the person who created it, the agent’s team manager, the manager’s manager, an admin, a partner who referred it, and a colleague who was asked to help with just this one lead. Access control is how a CRM encodes those answers so the lead list each person sees is right.

What is role-based access control (RBAC)?

In RBAC, each user has a role, and each role has a fixed set of permissions. An “agent” role can create leads and edit their own; an “admin” role can change settings and see everything. Roles are easy to understand and audit, and every CRM has them.

RBAC alone struggles with one kind of rule: permissions that depend on the relationship between a user and a specific record. “Managers can see leads” is a role rule. “Sam W.’s manager can see Sam W.’s leads, but not the other team’s” is a relationship rule. Encoding it with roles alone leads to one role per team, and then one role per exception.

What is relationship-based access control (ReBAC)?

In ReBAC, access follows from relationships between users and records, stored as facts such as “John Doe is assignee of lead 42”, “John Doe is member of team North”, “Jane Doe is manager of team North”, or “Example Co is viewer of lead 42”. Permissions are rules over those facts: a user can view a lead if they are its assignee, or manage its team, or it was shared with them.

The model was popularised by Google’s Zanzibar paper on its authorisation system, and open-source systems such as OpenFGA, SpiceDB and Permify implement it. A CRM does not need a separate authorisation service to use the idea: the relationships can live in the CRM’s own database.

RBAC vs ReBAC: what is the difference?

Role-based and relationship-based access control compared
RBAC (roles)ReBAC (relationships)
Access is based onThe user’s roleThe user’s relationship to the record
Example ruleManagers can edit leadsA team’s manager can edit that team’s leads
Sharing one recordHard; often a new role or a workaroundAdd one relationship: user is viewer of lead
Reporting linesNeeds many roles or groups“Manager of assignee” is one rule
Explaining access“Because of your role”“Because you manage the team that owns it”
Best forWhat a person may do in the appWhich records a person may see and change

In practice the two work together. Roles decide capabilities, such as importing, exporting or changing settings. Relationships decide which leads a person can see or edit.

What access patterns does a sales CRM need?

  1. Own leads: an agent sees leads assigned to them or created by them.
  2. Team leads: a team manager sees every lead in their team; members may or may not see each other’s leads, depending on the team.
  3. Reporting line: a manager sees the leads of the people who report to them.
  4. Single-lead sharing: a colleague, partner or branch gets view or edit access to one lead.
  5. Read-only partners: a viewer never edits, whatever they are shared.
  6. Admin override: admins and owners see everything, and can ask why a person can see a lead.

Why is access control hard for lead lists?

Checking one lead is easy. The hard case is the list: “show me page 40 of every lead I may see, filtered by stage and sorted by next follow-up”, over millions of leads. Checking each row one by one is far too slow. The practical approach is to turn the access rules into a database filter, so the list query only ever returns permitted rows and stays indexed. A single check and a list must use the same rules, or people will see leads in a list that they cannot open.

What should you check when choosing a CRM?

Access control checklist for a CRM evaluation
QuestionWhy it matters
Can agents be limited to their own leads?Protects your lead book when staff leave
Can a manager see only their team?Branches and teams often compete for the same buyers
Can one lead be shared without changing roles?Partners and helpers need narrow access
Is export a separate permission?Export is the easiest way to take a lead book
Can an admin see why someone has access?You cannot fix what you cannot explain
Is there an audit log?Shows who changed or exported what, and when

How does Swastik CRM do access control?

Swastik CRM combines both. Roles (owner, admin, manager, agent, viewer) decide capabilities such as import, export and settings; only owners, admins and managers can export. Relationships decide which leads each person sees: assignee, creator, team membership, team manager, reporting manager, and explicit view or edit shares on a single lead with a user or a team. The viewer role is always read-only. The same rules are compiled into the database query for lists, and admins can ask “why can this person see this lead?”. See access control features and security.

Frequently asked questions

What is ReBAC?
Relationship-based access control: access is decided by relationships between users and records, such as assignee of a lead or manager of a team, rather than by role alone.
Is ReBAC better than RBAC?
They solve different problems. RBAC is simple for app-wide permissions; ReBAC handles per-record rules like reporting lines and sharing. Most CRMs need both.
What is Zanzibar?
Google’s global authorisation system, described in a 2019 paper. It stores relationships as tuples and evaluates permissions from them; OpenFGA and SpiceDB are open-source systems inspired by it.
How do I stop salespeople seeing each other’s leads?
Limit agents to leads they are assigned to or created, and set team visibility so members do not see each other’s leads unless you choose to.
Can I share one lead with a partner without giving access to others?
In a CRM with record-level sharing, yes: add the partner as a viewer of that lead. In Swastik CRM, viewers are always read-only.