Single Sign-On / SAML

Enterprise authentication that lets your team log into Verabase using their existing company credentials (like Okta or Azure AD) instead of creating separate passwords.

Technical definition

SAML (Security Assertion Markup Language) 2.0 is an XML-based protocol for exchanging authentication data between an Identity Provider (IdP) and a Service Provider (SP). The IdP (e.g. Okta, Azure AD, Google Workspace) authenticates the user and sends a signed SAML assertion to the SP (Verabase), which grants access based on the assertion's attributes (email, groups, roles).

How Verabase uses SSO / SAML

Verabase supports SAML 2.0 SSO for Business and Enterprise plans. Configuration is in Settings → Security → SSO. You provide your IdP's metadata URL, and Verabase auto-configures the SAML endpoints. User provisioning can be automatic — when a new team member logs in via SSO for the first time, their Verabase account is created automatically with the role mapped from their IdP group. SSO enforcement can be required for all team members.

Why it matters for support teams

SSO is a security and compliance requirement for most enterprise organizations. It eliminates password fatigue, enables centralized access control, and ensures that when someone leaves the company, their Verabase access is revoked automatically through the IdP. For SOC 2 compliance, SSO is a standard 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.