Client workspaces
What a client workspace is in Metric Vault, the plan allowance, and the two ways agencies run multiple clients today.
Last updated 2026-08-06
Summary#
A client workspace is another Metric Vault account that you have been invited into and that appears in your Workspaces You've Joined list. Agency includes 15 client workspaces, Pro includes 1, and Enterprise is unlimited. This page explains what that relationship gives you today and how agencies actually keep several clients separate, so you can set your practice up once and correctly.
Purpose#
Agencies have a problem in-house teams do not: work for one client must not leak into the reporting for another, and the client relationship may end with the client keeping their own data. Metric Vault addresses that by making a workspace the same thing as an account, so a client's configuration can live under an account the client owns.
Overview#
There is no "create client workspace" button, because a workspace is an account. What creates the relationship between two of them is an invite, and the direction of the invite decides who holds the seat.
The client's account, you as a member. The client signs up, or you set the account up on their behalf, and that account invites you. Their workspace then appears in your Workspaces You've Joined list, and the seat comes out of the client's allowance rather than yours.
Your account, the client as a member. You invite the client's marketing lead into your own workspace. The seat comes out of your allowance, and they can co-author in your Blog Studio at the role you set. Only do this when your workspace is dedicated to that one client, because membership is all-or-nothing: see Roles and what each can do.
Either way, the mechanics are the ones in What teammates share. Membership shares the owner's Blog Studio and the member list. It does not merge the two accounts' data, and it does not merge their credits.
Plan allowance#
| Plan | Client workspaces | Team seats |
|---|---|---|
| Free | 0 | 1 |
| Pro | 1 | 5 |
| Agency | 15 | 15 |
| Enterprise | Unlimited | Unlimited |
Seats are what you feel first in practice, because every membership consumes a seat on the allowance of the account that sent the invite. An agency that invites clients into its own workspace is limited by its own seats; an agency that is invited into client-owned accounts is limited by each client's. See Seats and plan limits.
How it works#
Switching. Open Dashboard → Account & Team → Team and look at Workspaces You've Joined. Each row shows the workspace owner's address, your role in it and the date you joined. Click Switch → and confirm Switch to <address>'s workspace? The page will reload. The banner at the top of that card then reads Currently viewing: <address> (joined workspace), and your own workspace is always the first row so returning to it is one click. The choice is remembered in that browser and does not follow you to another device.
What switching does not do. It does not change the tool results, monitoring, alerts, scheduled reports or saved work your dashboard shows. Those always belong to the account you signed in as. Treat the switcher as a marker of which client you are working for, not as a change of data source.
What does not carry over. Your credits. Every tool run is charged to the account you are signed in as, so an agency running research across fifteen clients spends its own monthly allowance on all of it. Budget credits against your total client load, not per client. See How credits work.
Branding does not carry over either. White-label settings belong to the account that produced a report, so you configure your logo and colors once and every export and share link you create carries them, for every client. If a deliverable must look as though it came from the client rather than from you, it has to be produced from the client's own account. See White-label reports.
The two patterns that work#
One workspace, many clients. Run every tool against each client's domain from your own account. Every tool takes the domain or keyword as an input, so nothing about the toolset requires a separate workspace per client. Separate the output with white-labelled exports and per-client share links, and keep your monitoring and rank alerts for all clients on the one account where you will actually see them. This is the simplest setup and the one to choose unless you have a specific reason not to.
Client-owned accounts. Each client holds their own account and subscription, sets up their own monitoring and scheduled reports, and invites you so you can publish to their blog and appear on their team. The client keeps everything if the relationship ends. Choose this when the client wants to log in themselves, or when their data must not sit under your account.
You can combine them: run your research from your own account and hold a membership in the client's account for publishing.
When not to create a separate workspace#
Do not create one merely to keep reporting tidy — share links and white-labelled exports already do that, and a separate workspace adds a seat, an invite and a switching step. Do not invite several unrelated clients into one workspace of your own, because each of them would be able to publish into the same blog. And do not expect a separate workspace to give you a second credit allowance; it does not.
What is not included#
A branded, read-only client portal is not available. Client Portal appears in the Track & Report section of the sidebar so you can see where it will live, and the screen itself states that it is in development. Until it ships, give a client a view of their results with a public share link or a white-labelled export. See Sharing a result by link.
See also
Was this article helpful?
Thanks — feedback noted for the docs team.