Managing multiple client workspaces
How a partner works across several client organizations — one login with memberships in each, the organization switcher, per-org roles, and the honest limit that there's no single cross-org console.
If you implement or resell Vertiqa, you'll work across several client organizations. Here's exactly how that works today — and the one limit worth being straight about.
One login, many memberships
Each client is a separate organization on its own subdomain. Your single Vertiqa login can hold memberships in many organizations at once, so you don't juggle separate accounts per client.
To work inside a client's org, you have to be a member of it — either because you created the workspace during setup, or because the client's admin added you. Membership is always explicit: try to open an org you don't belong to and Vertiqa refuses with "You are not a member of that organization" (or "membership inactive" if your access was turned off). Nobody is silently granted access.
Choosing which client you're in
- At sign-in. If your login belongs to more than one organization, Vertiqa shows a Select Organization screen listing each one with its name, your role there, and its vertical. Pick one to drop into that client's workspace. (If you belong to just one, you go straight in.)
- While you're working. The organization switcher in the sidebar shows the org you're currently in and your role in it. Open it to switch to any other org you're a member of, jump to that org's Organization Settings, create a new organization, or sign out.
Your role is per-organization
Your permissions are scoped to each org independently — you might be owner in a client you set up and admin (or less) in another. Switching orgs switches your role and what you can see and do, because the isolation boundary holds per organization.
The honest limit: no single cross-org console
Vertiqa is one organization at a time. There is no partner console that aggregates all your clients into one pane — no combined pipeline across clients, no roll-up dashboard, no bulk action that reaches into every org at once. You switch into a client, work there, and switch out.
For most implementation and support work that's fine, because the work is inside one client's data anyway. But if a prospect's model depends on managing dozens of orgs from a single control plane, name this limit early rather than letting them assume it exists.