Skip to main content

Test and troubleshoot workspace access

Use separate test accounts for Owner, Admin, Member, and Viewer. Never validate permission boundaries using only hidden buttons; call the normal product workflow and confirm the server response.

  1. Create a disposable standard workspace and confirm its independent free billing state.
  2. Invite one Admin, Member, and Viewer from Settings → Team.
  3. Confirm that an unaccepted invitation does not expose the workspace.
  4. Accept each invitation with the exact invited and confirmed email.
  5. Test agent, call, knowledge, integration, team, settings, and billing access for each role.
  6. Switch between two workspaces and verify that lists, URLs, Vox threads, and balances change scope.
  7. Promote a second owner, then test leaving and removing the original owner.
  8. For an Agency workspace, open a child dashboard and verify the signed-in agency user retains attribution.

Common problems​

The wrong workspace is open​

Check /w/{workspaceId}/ in the URL, then use the workspace selector. The URL wins over the browser's stored last workspace when it names an accessible workspace. If it is inaccessible, Wirevox redirects to an accessible one.

An action returns Forbidden​

Confirm active membership, role, workspace ID, and the exact operation. Interface role descriptions are summaries; the enforced permission matrix is authoritative. Switching roles may require a context refresh or sign-in refresh before all UI controls update.

Admin cannot open Billing​

This is current behavior. Admin lacks workspace, agency, and subaccount billing permissions. Use an Owner account for billing.

Member cannot manage knowledge or integrations​

This is also current behavior even though the Team screen describes Member broadly. Member can manage agents and view calls, but not shared knowledge, numbers, integrations, functions, team, settings, or billing.

Check whether it is older than seven days, was resent or revoked, or was opened with a different email. Confirm the invited account's email before acceptance. Resending invalidates the previous token.

The invitation exists but no email arrived​

The record can survive an email-delivery failure. Check spam and provider delivery, then select Resend. In production, the configured frontend URL must also be correct.

The last owner cannot be changed or removed​

Promote another active member to Owner first. Then downgrade, remove, or leave with the original owner.

Workspace deletion is rejected​

Confirm another creator-owned workspace exists, not merely another workspace shared with you. For an agency, resolve child subaccounts. Also confirm your role satisfies the server manage check.

A removed user returns to onboarding​

They no longer have any workspace memberships. This is expected; they must accept another valid invitation or create a new workspace.