Skip to content

Added RBAC to SSO page #1078

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
stephenvapiai merged 1 commit into from
Jun 24, 2026
Merged

Added RBAC to SSO page #1078

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions fern/security-and-privacy/sso.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,20 @@ Once SSO is enabled for your organization, Vapi provides your IT administrator w

Vapi does **not** support SCIM provisioning. When a user signs up, they create their own Vapi account; your IT administrator then invites them into your organization. Permissions are managed within Vapi using **Role-Based Access Control (RBAC)** at the application layer.

## Role-based access control (RBAC)

RBAC controls what each member can do in your organization. You assign a role when you invite a member to your organization.

Three roles are available:

| Role | Access |
|------|--------|
| **Admin** | Read and write everything |
| **Editor** | Read and write everything **except** Org Settings, Billing, Members, and API Keys. |
| **Viewer** | Read-only access to everything **except** Org Settings, Billing, Members, and API Keys. |

Use **Editor** to give developers full build and test access without exposing billing or member management.

## Need help?

To enable SSO or ask about configuration, talk to the [Vapi sales team](/enterprise/plans).
Loading