Role-Based Access Control

A permission system that controls what each team member can see and do in Verabase based on their assigned role — Admin, Agent, or Viewer.

Technical definition

RBAC assigns permissions to roles rather than individual users. Each role defines a set of allowed actions (create, read, update, delete) on specific resources (agents, knowledge base, settings, conversations). Users are assigned one or more roles, and their effective permissions are the union of all role permissions. This is simpler and more auditable than per-user permission assignment.

How Verabase uses RBAC

Verabase has three built-in roles: Admin (full access to settings, billing, and configuration), Agent (access to Live Inbox, conversations, and knowledge base), and Viewer (read-only access to analytics and conversations). Custom roles are available on Enterprise plans. Role assignments are managed in Settings → Team. When SSO is enabled, roles can be automatically mapped from your IdP's group attributes.

Why it matters for support teams

Without RBAC, every team member has full access to everything — a security risk and a compliance violation. RBAC ensures that support agents can't accidentally change AI configurations, that viewers can see analytics without accessing customer conversations, and that only admins can modify billing or security settings. It's a SOC 2 requirement.

Related terms

How Verabase Handles Self-Healing Knowledge

The standard industry approach relies on support agents manually flagging stale content and technical writers updating documentation weeks later. Verabase completely upends this model through an autonomous AI platform that identifies knowledge gaps the moment an AI agent encounters a question it cannot answer.

Rather than requiring manual intervention, our visual RAG engine drafts a proposed fix. It analyzes the context of the user's question, reviews your existing knowledge base for conflicts, and creates a clear, structured article or snippet. All you need to do is click 'Approve'. This ensures your AI agents continually get smarter over time without adding to your support team's workload.

Security First Architecture

Many legacy platforms bolt AI onto their existing infrastructure, creating potential data leaks between tenants or exposing sensitive internal documents to end-users. Verabase is built from the ground up with a Bring Your Own Key (BYOK) architecture, enterprise-grade access controls, and strict semantic boundaries. This means your private engineering documents never accidentally leak into customer-facing agent responses.