Users and teams
Path: /admin-settings → Users and Teams tabs
Platform-wide management of user accounts and teams. Distinct from Team settings → Users, which scopes to a single team.
Users tab
| Column | Description |
|---|---|
| First / Last Name | The user's name. |
| Login email. | |
| Active | Whether the account can log in. |
| Teams | (SUPERUSER) team memberships with roles. |
Management
- Create user — name + email; assign to teams with roles. The user receives a welcome / password-setup email if mail is configured.
- Edit user — name, email, active status, team memberships.
- Default team — which team is auto-selected on login.
- Deactivate — set active = false. The user can no longer log in.
Teams tab (SUPERUSER)
| Column | Description |
|---|---|
| Name | Team name. |
| Base Numbers | Assigned base numbers. |
| Apps | Number of apps in the team. |
Team configuration
| Field | Description |
|---|---|
| Name | Unique team name. |
| Base Numbers | Multi-select of base numbers the team can use for PSTN endpoints. |
| Users | Members with roles (ADMIN / MEMBER / VIEWER). |
| Server Groups | Multi-select of server groups available to this team. |
| Recording Enabled | Default for team's apps (can also be toggled per-app). |
| SMS Enabled | Whether SMS features are available (default true). |
| Notifications | JSON config — thresholds and recipients. |
Teams support soft deletion — deactivated teams carry a Deleted At timestamp and are excluded from active lists. New teams may be provisioned with a default dashboard / example app depending on deployment settings.
API access configuration
Controls how the team uses API keys:
| Field | Description |
|---|---|
| Allowed API Scopes | Multi-select (e.g. CREATE_CALL_TOKEN, READ_CALL_TOKEN). |
| Max API Keys | Max keys the team can create (default 2). |
| Max Requests Per Day | Daily rate limit per team. null = unlimited. |
Sync all apps
Pushes every app config in the team to Redis. Useful after platform-wide changes (e.g. server group config) or to recover from drift.
SUPERUSERs review authentication and role-management audit events on the dedicated Access logs tab (/admin-settings/access-logs).
Workflows
Create a user
Click Create, enter name + email, assign team memberships with roles, set a default team, save.
Create a team
(SUPERUSER) Teams tab → Create → name → assign base numbers → add users with roles → configure API access if needed → assign server groups → save. Default dashboard / example app provisioning may run automatically.
Enable API access for a team
Edit the team → API Access Configuration → select scopes, max keys, optional daily limit → save. The team's ADMINs can now create keys in Settings → API Keys.