What a Workspace Contains
Each workspace has its own:- Voice agents
- Phone numbers
- Call history and recordings
- API keys
- Billing usage (wallet is shared at the account level, but usage is tracked per workspace)
- Telephony Config for enabled providers, destination network groups, SIP/BYOC routing, and visible telephony rates
- Team members and their roles
- Webhook configurations
- Post-call analysis templates
Common Use Cases for Multiple Workspaces
Environment separation
Use separate workspaces for Development, Staging, and Production. This prevents test calls from appearing in production analytics and test configurations from affecting live agents.
Client isolation
Agencies managing voice agents for multiple clients use a workspace per client. Each client’s data, agents, and numbers are fully isolated.
Business unit separation
Large organizations separate departments (Sales, Support, Operations) into individual workspaces, with different team members and permissions per workspace.
Product separation
Companies with multiple products use a workspace per product, keeping the agents, numbers, and analytics for each product cleanly separate.
Creating a Workspace
Open workspace switcher
Click the workspace name in the top-left corner of the dashboard. A dropdown appears showing all your current workspaces.
Name the workspace
Enter a name for the workspace (e.g., “Production”, “Client: Acme Corp”, “Staging”). Names must be unique within your account and can be changed later.
Select the region
Choose the data region for this workspace. For Indian data residency requirements, select the India region. The region cannot be changed after workspace creation.
The number of workspaces you can create depends on your plan. Starter plans typically allow 2 to 3 workspaces. Professional and Enterprise plans have higher or unlimited workspace counts.
Switching Between Workspaces
Click the workspace name in the top-left corner of the dashboard and select the workspace you want from the dropdown. The dashboard reloads in the context of the selected workspace. Your active workspace is always visible in the top-left corner. All actions you take (creating agents, purchasing numbers, viewing call history) apply to the currently active workspace.Workspace Settings
Access workspace settings at Settings → Workspace (while the workspace is active).Workspace Name
Update the display name of the workspace. This is purely for your reference in the dashboard.Default Agent Settings
Configure defaults that apply to new agents created in this workspace:- Default LLM model
- Default transcriber
- Default TTS provider
- Default max call duration
- Default recording setting
Notification Webhooks
Configure a workspace-level webhook URL that receives all call lifecycle events for every agent in the workspace. This is useful for centralized logging and monitoring systems that need to receive events from all agents without configuring a webhook per agent.Telephony Config
Use Workspace Settings > Telephony Config to control which telephony paths are enabled for the workspace.| Control | What it does |
|---|---|
| Telephony provider | Selects the provider whose routes you want to review, such as Plivo or SIP/BYOC. |
| Country list | Shows countries that have network groups for the selected provider. |
| Network group status | Enables or disables a destination network group for outbound validation and routing. |
| Inbound and outbound price | Shows the INR rate for that network group when your billing plan exposes telephony rates. |
| SIP/BYOC status | Enables or disables SIP/BYOC routing at the provider level. SIP/BYOC uses a flat rate when billing rates are configured. |
New workspaces can receive default enabled network groups for the default provider. Review Telephony Config before launching international or large outbound campaigns.
Workspace Deletion
To delete a workspace:- Remove all active agents and release all phone numbers from the workspace first
- Go to Settings → Workspace → Danger Zone
- Click Delete Workspace
- Type the workspace name to confirm
Inviting Team Members
You can invite other DialNexa users to collaborate in a workspace. Each member has a role that determines what they can do within that workspace.Available Roles
| Role | What they can do |
|---|---|
| Owner | Full access, including billing and workspace deletion. Only one Owner per workspace. |
| Admin | Create/edit/delete agents, manage phone numbers, invite members, view call history. Cannot manage billing. |
| Member | Create and edit agents, view call history. Cannot delete agents, manage numbers, or invite members. |
| Viewer | Read-only access: view agents and call history, cannot make any changes. |
Sending an Invitation
Enter the email address
Enter the email address of the person you want to invite. They do not need to have a DialNexa account yet, and they will be prompted to create one.
Accepting An Invitation
Invitation links open the/invite page. DialNexa verifies the token before adding the user to the workspace.
| State | What the invitee sees |
|---|---|
| Not signed in | They are asked to sign in or create an account with the invited email address. |
| Signed in with the invited email | DialNexa accepts the invite and redirects them to the dashboard. |
| Signed in with a different email | DialNexa asks them to sign in with the invited account. |
| Already a member | DialNexa shows that they already belong to the workspace. |
| Expired or invalid link | DialNexa asks them to request a new invitation. |
Managing Existing Members
From Settings → Team → Members, you can:- Change a member’s role by clicking their current role and selecting a new one
- Remove a member by clicking Remove on their row
- View each member’s last active date
Workspace-Level API Keys
API keys are workspace-scoped: a key created in Workspace A can only access resources in Workspace A. To interact with multiple workspaces programmatically, create a separate API key for each workspace. Enterprise accounts can create organization-level API keys that have cross-workspace access. See Organization and Members.Related Pages
- Access Control: detailed role permissions
- API Keys: creating workspace-scoped API keys
- Data Residency: choosing the India region for a workspace