Team & organization management
Every Stellar account belongs to an organization, an isolated workspace where your team collaborates on building and managing AI agents. Navigate to Settings > Organization to manage team members, assign roles, and configure organization-level settings. For details on sign-in methods and SSO configuration, see Authentication.
Organization structure
An organization is your isolated workspace in Stellar. Multiple users can work together within the same organization, sharing resources while usage is tracked and billed at the organization level.
Team members
The Settings > Organization page displays all current members in a table showing each person's name, email, and role assignments per scope.
Adding members
Admins can add new members by clicking Add member. The form asks for the person's first name, last name, and email address, then presents a role selector for each product scope. The new member receives access immediately, no invitation email is required. New members default to Voice Viewer with no access to other scopes unless the admin explicitly assigns additional roles.
Editing roles
Admins can change any member's role directly from the members table using the inline role dropdowns. Each scope has its own dropdown, so you can adjust Voice, Email, Call analysis, and Organization roles independently. You cannot edit your own roles.
Removing members
Admins can remove a member by clicking the delete icon in the Actions column. A confirmation dialog appears before the removal is finalized. You cannot remove your own account.
SAML organizations
In organizations that use SAML SSO, the user lifecycle is managed entirely by the identity provider. Adding members, editing roles, and removing members is not possible through Studio. See the authentication page for details on SAML role provisioning.
Roles and permissions
Each user is assigned a role per product scope. Roles are independent across scopes, so a user can be an Admin for Voice but a Viewer for Email. Three assignable roles:
- Viewer: read-only access to the scope's resources.
- Editor: can manage core resources (like agents) but cannot change configuration or settings.
- Admin: full access including configuration, connectors, and settings.
A role can also be set to None, which removes access to that product entirely. When a user has no role for a scope, the corresponding menu items and pages are hidden.
The table below summarizes what each role can do within each scope.
| Scope | Viewer | Editor | Admin |
|---|---|---|---|
| Voice | View agents, connectors, conversations, analytics | Manage agents; view connectors, conversations, analytics | Full access including SIP configuration |
| View email agents, connectors, received emails | Manage email agents; view connectors, emails | Full access to email agents, connectors, emails | |
| Call analysis | View recorded calls, reports, groups | View recorded calls, reports, groups | Full access to recorded calls, reports, groups |
| Organization | View members, settings, secrets, API tokens | View members, settings, secrets; manage API tokens | Manage members, settings, secrets, API tokens; view billing |
Organization settings
Below the members table, admins can configure additional organization-level settings.
Data retention controls how many days conversation data is kept before deletion. This setting is currently managed by the Stellar team; contact support to adjust it.
Authentication methods lets admins choose which sign-in methods are available to organization members. See the authentication page for available methods and configuration details.