Understand workspace types and isolation
Wirevox uses one workspace model with three current types.
| Type | Purpose | Parent |
|---|---|---|
| Standard | An independently operated business or location | None |
| Agency | An agency's own control and billing workspace | None |
| Subaccount | A customer workspace managed under an agency | One agency workspace |
An Agency subscription changes the subscribed workspace to type agency. A subaccount is created from that agency and records its agency as parent_workspace_id.
Resources do not cross automatically
An agent can use only compatible knowledge, functions, integrations, numbers, and other resources from its own workspace. Identically named resources in two workspaces are still separate records.
Operational data is also scoped. Switching workspaces changes the calls, Website Chat conversations, contacts, analytics, usage, and Vox threads you are viewing. Never infer the workspace from a resource name; use the workspace ID in the URL and the active-workspace selector.
Access is membership-based
The accessible-workspace list includes workspaces where the user has an active membership, as well as legacy creator-owned workspaces. Pending invitations do not grant access.
For a subaccount, an owner or admin of its parent agency can receive implicit admin access even without a direct subaccount membership. This is the server-side basis for the agency Open Dashboard support workflow.
Billing boundaries
New standard workspaces are created independently on the free tier and are billed independently. An agency and each subaccount remain distinct usage scopes even when the agency allocates credits or assigns a customer package.
Do not combine current balances merely because workspaces share an owner. For agency allocation and attribution details, see Understand agency and subaccount billing.
URL scope
Authenticated workspace pages use:
/w/{workspaceId}/{page}
If the URL contains an inaccessible workspace ID, the application redirects to an accessible workspace rather than treating the URL as authorization.