Workspaces, members, and permissions
A workspace is Wirevox's primary security, ownership, resource, and billing boundary. The active workspace controls which agents, knowledge bases, functions, integrations, phone numbers, conversations, contacts, analytics, Vox chats, and balances the application can access.
Signed-in user
|
+-- active membership --> Workspace
|
+-- role --> server permissions
+-- resources and operational records
+-- subscription, credits, and usage
Being signed in is not enough to access a workspace. Wirevox resolves an active membership and checks an accepted server permission for each protected operation.
In this topic
- Understand workspace types and isolation — compare standard, agency, and subaccount workspaces and their ownership boundaries.
- Create, configure, and switch workspaces — review creation, URL scope, stored selection, settings, and independent billing.
- Understand roles and permissions — use the enforced server permission matrix rather than broad role labels.
- Invite and manage members — send, accept, resend, change, revoke, remove, and leave safely.
- Manage agency workspaces and subaccounts — understand parent-child hierarchy, support access, branding, settings, packages, and credit allocation.
- Delete or leave a workspace — distinguish membership removal from destructive workspace deletion.
- Test and troubleshoot access — diagnose forbidden actions, wrong workspace data, invitation errors, role mismatches, and ownership guards.
Source of truth
The backend permission check is authoritative. Interface visibility and short role descriptions are helpful summaries, but they do not grant access and can be broader than the currently enforced permission set.