Saltar al contenido
Glosario November 2026 7 lectura de minutos

¿Qué es el control de acceso basado en roles (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.

D
November 2026

Respuesta rápida

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?

  1. List the permissions. Each is one action on one kind of thing, such as listening to a recording.
  2. Group them into roles. A role is a named bundle matching a job.
  3. Assign roles to users. A user may hold more than one.
  4. The system checks the role on every action. No matching permission, no access.
  5. Review the grid regularly. Roles drift as jobs change.

What Roles Does a Contact Centre Need?

RoleTypical needs
AgenteHandle calls and their own records; no access to other teams' data or settings
SupervisorMonitor live calls, review recordings, coach; see herramientas de supervisión
AdministraciónConfigure 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

ModeloDecides byFits when
RBACThe user's roleJobs are clear and stable
ABACAttributes of user, resource and context (NIST SP 800-162: subject, object and environment conditions)Rules depend on many conditions
Per-user permissionsThe individualSmall teams; hard to review as they grow

How Does DialerBee Handle Roles?

El seguridad y acceso 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 arquitectura multiusuario. Los página de confianza y solución empresarial give the wider view.

Preguntas frecuentes

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.

Fuentes

Lecturas relacionadas: Seguridad y acceso · Multiusuario · Arquitectura multiusuario · Confianza · Herramientas de supervisión · Enterprise

This page is general information, not legal advice. DialerBee does not provide legal advice or guarantee regulatory compliance.

Términos relacionados

¿Listo para ver DialerBee en acción?

Solicite una demostración en vivo de 15 minutos o comience una prueba gratuita de 14 días: sin presentaciones, sin compromiso. Las llamadas empiezan en cuanto su propia troncal SIP o PBX está conectada y aprobada.

Prueba gratuita de 14 días · crédito de IA gratuito · sin tarjeta · 11 idiomas · BYOC · controles que apoyan el cumplimiento

Ver el sitio completo en inglés →