Skip to content

User Management

Open in ChatGPT Open in Claude

Roles and permissions control what each teammate can see and change. Invite a user with a baseline role, then narrow or widen their access per feature when they need something different from the preset.

Start every invite with a baseline role. It sets a sensible default across all features, which you can adjust afterward.

RoleAccessBest for
ViewerRead access across configured features. No changes to settings or content.The safe default for most observers.
EditorUpdates content and configuration, without broad account-wide admin access.Day-to-day operators.
AdminFull administrative control, including high-impact settings.Trusted owners. Grant it only when necessary.

Every feature is governed by one of four levels. A baseline role sets these for you; custom access lets you set them per feature.

LevelWhat it grants
No PermissionThe feature is hidden. The user can’t see or open it.
ViewerRead-only. The user can see the feature but can’t change it.
EditorThe user can view and change the feature’s content and configuration.
AdminFull control of the feature, including its high-impact settings.

Not every feature offers all four levels. Some are view-only, and some skip Editor or Admin where the level wouldn’t mean anything. The available levels for each feature are listed below.

Access is granted per feature. Each row is one selector in Customize Access; the levels shown are the ones that feature supports (every feature also supports No Permission).

FeatureGovernsAvailable levels
Agent ConfigurationHow the agent is set up and behaves.Viewer, Editor, Admin
Agent KnowledgeThe Knowledge Base that powers answers and actions.Viewer, Editor
Agent ActionsThe actions the agent can run.Viewer, Editor, Admin
Agent ConversationsConversation history and transcripts.Viewer
AI API KeyThe AI provider key the agent runs on.Viewer, Admin
Subscription SettingsPlan and subscription settings.Viewer, Editor
Session ReplaySession replays of user sessions.Viewer
Feature ManagementFeature management and flags.Viewer, Editor, Admin
AnalyticsConversational Analytics dashboards and reports.Viewer, Admin
JWT SettingsJWT authentication settings.Viewer, Editor, Admin
  1. Open Invite User and enter the person’s Name and Email.

  2. Under Choose Access Level, pick a baseline role (Viewer, Editor, or Admin). This fills in a default permission for every feature.

  3. Optional: open Customize Access to override individual features. Only do this if the person needs something different from the preset.

  4. Check the Effective Access panel, which summarizes exactly what the invite grants, then send the invite.

Access isn’t fixed at invite time. To change it later, open Edit for that person from your team list. The controls are the same as the invite dialog: adjust the baseline role or set individual features under Customize Access, watch Effective Access update, then Save.

Customize Access is for the exceptions, when one person needs more or less than any single role gives. Open Show Advanced, search for a feature, and set its level independently using the feature reference above. Each feature offers only the levels that apply to it.

Setting any feature to a level that doesn’t match the chosen role marks the user as Custom access in use, so it’s clear this person isn’t a plain Viewer, Editor, or Admin.

The Effective Access panel is the source of truth for an invite or edit. It shows a running count of permissions selected (for example, “20 permissions selected”) and lists every feature with the level the user ends up with, after the baseline role and any custom overrides are combined. Confirm it reads as intended before you save.