Skip to main content
Agent Studio offers granular permission control, allowing you to mix access levels across different areas for each user. users

Account roles

Admin

users-admin Admins have full access to all workspace features:
  • Manage all projects and configurations
  • Invite and remove users
  • Modify user permissions
  • Access billing and account settings
  • Full edit access to all navigation areas
  • Use Studio Assistant on enterprise clusters
Studio Assistant is available only to project admins on enterprise clusters. Permissions will become more granular over time.

Member

Members have permission-based access determined by their assigned settings:
  • Access controlled per navigation area
  • Can have different permission levels for different sections
  • Cannot manage other users or account settings

Permission levels

users-permissions Each navigation area supports three access levels:

Analytics

Control access to conversation data and analysis tools.

Behavior

Control access to agent personality, language, guardrails, and model selection.

Knowledge

Control access to FAQs, external sources, and variants.

Flows

Control access to conversation flow design (no-code and code-based).

Tools

Control access to custom Python functions, classes, and tool integrations.

Testing

Control access to test cases, test sets, and regression runs.

Real-time config

Control access to real-time config tools and the configuration builder.

Voice

Control access to all voice channel settings.

Messaging

Control access to chat and SMS settings.

Integrations

Control access to API integrations, third-party service connections, and MCP.

Deployments

Control access to environment and version management.

Widgets

Control access to phone and chat widget configuration, installation, and sharing.

Account

Control access to account settings, users, API keys, call data, and legal.

Setting permissions

  1. Go to the Users tab on the workspace homepage.
  2. Select a user or click Invite for new users.
  3. For each navigation area, select None, Read, or Edit.
  4. Expand sections for more granular control.
  5. Save changes.
Start with broad area permissions, then expand sections to fine-tune access where needed.

Common configurations

user-permissions-applied

Read-only reviewer

Knowledge editor

Full developer

Operations manager

Permission inheritance

  • If a parent area is set to None, all sub-sections are inaccessible
  • Setting a parent area to Edit grants edit access to all sub-sections unless overridden
  • Sub-section permissions can be more restrictive than the parent, but not less restrictive

User management

Getting started with permissions and account-level roles.

Invite users

Add new team members with role-based access control.
Last modified on July 17, 2026