User management

Manage team access and permissions for your PolyAI account.

Use user management to control who can access, edit, and deploy your agent. Without proper permissions, anyone on the team can push changes to production or access sensitive conversation data.

Access user management from the Users tab in the workspace top bar (Agents / Users / Usage / API Keys / Secrets) — a workspace-level area separate from the per-agent sidebar.

Inviting users

Add colleagues to your account to collaborate on building and managing agents. Each user can be assigned permissions that determine their level of access to different areas of Agent Studio.

See Invite users for step-by-step instructions.

Granular permissions

Agent Studio supports mixed permissions across different navigation areas. Give users edit access where they build, and restrict access where they only need visibility.

Permission levels

Each navigation area can be set to one of three access levels:

Level	Description
None	User cannot see or access this area
Read	User can view content but cannot make changes
Edit	User can view and modify content

Navigation areas

Set permissions for each major section of Agent Studio:

Area	What it controls
Home	Studio Assistant, the natural-language builder
Analytics	Custom metrics
Conversations	Full conversation history with PolyScores, search and filtering
Custom Dashboards	Custom dashboards
Knowledge	FAQs, Sources, Variants
Flows	Structured, step-by-step user journeys
Tools	Reusable functions and API actions
Testing	Simulation tests across all channels
Voice	All voice settings
Messaging	Messaging channel settings (webchat, SMS, email etc.)
Integrations	App integrations, APIs and MCP connections
Deployments	Deployments, deployment history and A/B tests
Widgets	Widgets across channels and surfaces
Account	Account settings

Expandable sections

For more specific control, expand any section to set permissions on individual items. For example:

• Expand Analytics to set separate permissions for Conversations vs Smart Analyst
• Expand Knowledge to allow Edit on FAQs but Read-only on Sources

For example, give QA teams read access to Conversations while restricting access to building areas.

Example permission configurations

See role permissions for ready-made configurations for common roles like content editors, QA analysts, and voice specialists.

Account-level roles

In addition to granular permissions, users have an account-level role:

Role	Description
Admin	Full access to all features, including user management and billing
Member	Access determined by assigned permissions

Admins can manage other users and configure account-wide settings. Members’ access is controlled by the granular permission settings described above.

Security

• User permissions are scoped to your account
• Sensitive data is only accessible to authorized users based on their assigned permissions
• Permission changes take effect immediately
• Audit logs track permission modifications (for Enterprise accounts)

SSO does not control permissions. If your account uses Google SSO for sign-in, it only handles authentication. User roles and granular permissions must still be managed manually in the Users tab on the workspace homepage. SSO sign-in does not automatically assign Admin or Member roles, nor does it set navigation area permissions. If you notice unexpected changes to user permissions, contact your PolyAI representative for assistance.

Related pages

Role permissions

Detailed permission reference and common configurations.

Invite users

Add team members with role-based access control.