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 center, 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. The assignable roles are:
- Support: read-only access to operational data such as conversations, emails, and reports, without visibility into agent configuration. Ideal for support staff who review interactions but do not manage AI agents.
- Viewer: read-only access to the scope's resources, including agent configuration.
- Editor: can manage core resources (like agents) but cannot change configuration or settings.
- Admin: full access including configuration, connectors, and settings.
- Agent: for the people who pick up calls. On the Call center scope, they work the console: they take calls from the queues they are staffed on, and afterwards see the calls they handled and nothing else. On the Voice scope, they see only the Handover view, with the caller, the AI's summary and reason for transferring, the captured facts, and the transcript, so they can take over a live call with full context. Neither can see agent configuration, analytics, or unrelated conversations. Available on the Voice and Call center scopes only.
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 | Support | Viewer | Editor | Admin |
|---|---|---|---|---|
| Voice | View conversations and analytics | View agents, connectors, conversations, analytics | Manage agents; view connectors, conversations, analytics | Full access including SIP configuration |
| View and update received emails; view analytics | View email agents, connectors, received emails | Manage email agents; view connectors, emails | Full access to email agents, connectors, emails | |
| Chat | View chat conversations | View chat agents and conversations | Manage chat agents; view conversations | Full access to chat agents and conversations |
| Call center | Answer calls from the console; view the live dashboard for the queues you staff; view the calls you handled | View call center configuration and calls in your groups | View call center configuration and calls in your groups | Manage queues, agents and settings; answer calls from the console; view calls in your groups; manage routing flows and schedules |
| Call analysis | View recorded calls, reports, groups | View recorded calls, reports, groups | View recorded calls, reports, groups | Full access to recorded calls, reports, groups |
| Organization | No access | View members, settings, secrets, API tokens | View members, settings, secrets; manage API tokens | Manage members, settings, secrets, API tokens; view billing |
On Call center, Support is the role for the people who actually work the phones. It means something different here than in the other scopes: rather than a read-only tier, it grants the console, where an agent answers and handles calls, plus the live dashboard for the queues they staff, a history of the calls they handled, and nothing on the configuration surface.
The live dashboard is a shared view of the queues they staff, not a personal one. It shows the callers waiting right now, including their phone numbers, so an agent can pick up the next call, alongside how those queues are doing against your service level and which calls that agent handled most recently. Someone staffed on a queue can therefore see who is calling in on it, whether or not they end up taking the call.
The Agent role is not shown above because it now applies to the Voice scope only, where it grants read-only access to the Handover view (handed-over calls and their transcripts) and nothing else. It is being retired in favour of Support.
Voice and call center are separate
Running an AI voice agent and running a call center are two jobs, and they have their own roles. Someone who builds and tunes your voice agents needs a Voice role. Someone who staffs the queues, answers calls, or reports on how the call center is performing needs a Call center role. A person doing both gets one of each.
The Call center scope only appears for organizations with the call center enabled. Ask your Stellar contact if you do not see it.
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.