What Is Role-Based Access Control (RBAC)?
Role-based access control (RBAC) grants permissions to roles, then roles to users. Learn how RBAC works in a call center for agents, supervisors and admins.
Risposta rapida
Role-based access control (RBAC) gives permissions to roles instead of to individuals, then assigns roles to users. NIST describes it as each user having one or more roles and each role having one or more privileges. In a call center it keeps agents, supervisors and admins to the powers their jobs need.
Vendor security reviews almost always ask how access is controlled. RBAC is the usual answer. This page explains the idea and how it applies to a contact centre.
What Is Role-Based Access Control?
NIST's description of role-based access control says each user is assigned one or more roles, and each role is assigned one or more privileges that are permitted to users in that role. The model was standardised as ANSI/INCITS 359-2004, adopted February 11, 2004, and revised as INCITS 359-2012, dated May 29, 2012.
The benefit is simple. When someone changes job, you change their role, not dozens of individual settings.
How Does RBAC Work?
- List the permissions. Each is one action on one kind of thing, such as listening to a recording.
- Group them into roles. A role is a named bundle matching a job.
- Assign roles to users. A user may hold more than one.
- The system checks the role on every action. No matching permission, no access.
- Review the grid regularly. Roles drift as jobs change.
What Roles Does a Contact Centre Need?
| Role | Typical needs |
|---|---|
| Agente | Handle calls and their own records; no access to other teams' data or settings |
| Supervisore | Monitor live calls, review recordings, coach; see strumenti di supervisione |
| Amministratore | Configure campaigns, users, lists and settings for the company |
The exact split is your decision. The point is that nobody holds more power than the job requires.
RBAC vs Other Access Models
| Modello | Decides by | Fits when |
|---|---|---|
| RBAC | The user's role | Jobs are clear and stable |
| ABAC | Attributes of user, resource and context (NIST SP 800-162: subject, object and environment conditions) | Rules depend on many conditions |
| Per-user permissions | The individual | Small teams; hard to review as they grow |
How Does DialerBee Handle Roles?
IL sicurezza e accesso page states a per-tenant role matrix of 11 permission categories and 41 permissions with one column per role, edited per tenant, and an audit log that records the user and IP address. The roles it lists are platform admin, partner admin, admin, supervisor, team lead, agent and booking viewer. Each company's data stays separate through multi-tenant design; see architettura multi-tenant. The pagina di fiducia E soluzione aziendale give the wider view.
Domande frequenti
What is RBAC?
Role-based access control. Each user is assigned one or more roles, and each role is assigned one or more privileges permitted to users in that role.
What is the RBAC standard?
NIST lists ANSI/INCITS 359-2004, adopted February 11, 2004, and its revision INCITS 359-2012 dated May 29, 2012.
What is the difference between RBAC and ABAC?
RBAC decides by role. Attribute-based access control, in NIST SP 800-162 terms, grants or denies a request based on attributes of the subject, attributes of the object, environment conditions and policies written in those terms. The two models are not exclusive; ask a vendor which one it uses.
Why does a call center need RBAC?
Agents, supervisors and administrators need different powers over recordings, numbers, lists and settings. Roles keep those powers separate and easy to review.
How many roles does DialerBee have?
Seven are listed on the security and access page: platform admin, partner admin, admin, supervisor, team lead, agent and booking viewer.
Does RBAC alone secure a platform?
No. It is one control. Audit logs, tenant isolation and key handling matter too.
Fonti
- NIST CSRC, Role Based Access Control project (archived) (source, checked 2026-11-19)
- NIST CSRC Glossary, attribute based access control (definition from NIST SP 800-162) (source, checked 2026-11-19)
Letture correlate: Security and access · multi-tenant · Architettura multi-tenant · Fiducia · Strumenti di supervisione · Enterprise
This page is general information, not legal advice. DialerBee does not provide legal advice or guarantee regulatory compliance.
Termini correlati
What Is RTP (Real-time Transport Protocol)?
RTP carries the actual voice in a VoIP call, while SIP only sets it up. See what RTP does, how RTCP reports loss and jitter, and why one-way audio happens.
Che cosa sono il livello di servizio (SL) e l'accordo sul livello di servizio (SLA)?
Il livello di servizio è la quota di contatti risposti entro un tempo target. Formula, significato dell'80/20, differenza con l'SLA e cosa lo distorce.
What Is SIP (Session Initiation Protocol)?
SIP is the signalling protocol that sets up, changes and ends VoIP calls. Learn how a SIP call works, how it differs from RTP, and how dialers use it.
Che cos'è il routing basato sulle competenze?
L'instradamento basato su competenze assegna ogni chiamata inbound a un operatore con lingua, prodotto o qualifica giusti. Funzionamento e alternative.
Che cos'è l'analisi vocale?
L'analisi vocale trasforma le trascrizioni in dati ricercabili: sentiment, parole chiave, riepiloghi e flag di conformità. Come funziona e i suoi limiti.
What Is SRTP (Secure RTP)?
SRTP encrypts the voice in a VoIP call and protects it from tampering and replay. Learn how SRTP works with SIP over TLS and what to ask of a SIP trunk.
Pronti a vedere DialerBee in azione?
Richiedi una demo dal vivo di 15 minuti oppure avvia una prova gratuita di 14 giorni: niente slide, nessun impegno. Le chiamate partono quando il tuo trunk SIP o PBX è collegato e approvato.
Prova gratuita di 14 giorni · credito IA gratuito · senza carta · 11 lingue · BYOC · controlli a supporto della conformità