Workspaces explained

Summary#

A workspace is the container for everything one account owns: monitored URLs, rank alerts, scheduled reports, saved results, competitor and keyword lists, white-label branding, and blog sites. Every account owns exactly one, created automatically at signup and identified by the owner's email address. On plans with seats you can invite people into yours, and you can accept invitations into other people's. This page explains what crosses that boundary, what does not, and who pays for what.

Purpose#

Collaboration models usually fail in one of two ways. Either everything is shared, so one person's experiment pollutes everyone's data, or nothing is shared, so a team of four maintains four disconnected copies of the same competitor list.

Metric Vault draws the line at the workspace. Inside one, the monitoring configuration and the shared analyses are common ground, so a teammate who joins on Tuesday immediately sees the competitor URLs you set up on Monday. Outside it, nothing leaks. Two people in different workspaces cannot see each other's work at all, which is what makes the model safe for an agency running several clients.

Overview#

There is no screen called "create a workspace" and there does not need to be. The model is deliberately lightweight:

• Your email address is your workspace. Signing up creates it.
• Any other person is either not in it, or an accepted member of it.
• You can simultaneously be the owner of your own workspace and a member of several others.
• The workspace you are currently looking at is shown on the Team screen as Currently viewing: <email> (your own workspace) or (joined workspace).

Ownership is intrinsic to whoever created the workspace. It cannot be handed over, and no role can be granted that makes someone else the owner. See Workspace ownership.

How it works#

What members share#

An accepted member sees the owner's workspace data. The Team screen states this plainly: teammates "get access to your monitored URLs, rank alerts, scheduled reports, shared analyses, and white-label branding."

Seats, and who can invite#

A seat is an invited member. The owner is not counted against the cap.

Pending invitations consume a seat from the moment they are sent, not from the moment they are accepted. If you are at the cap and someone has not responded, remove the pending invite before sending another.

Attempting to invite without seats returns:

Team invites require the Pro plan or higher. Your account is on Starter.

Attempting to invite past the cap returns:

Team seat limit reached (<cap> members on the <Plan> plan). Upgrade for more seats.

Seats and plan limits covers the caps in detail.

Inviting someone#

Go to Account & Team → Team. In the Invite a Teammate card, enter the address in EMAIL ADDRESS (placeholder teammate@company.com), choose a role, and press Send Invite.

The dropdown is labelled BLOG ROLE and offers three options:

The invited person receives an email with an accept link, provided email delivery is configured. If it is not, the app tells you so and gives you the invite URL to send manually: Invited <email> — copy this invite URL to send manually.

Other messages you may see: You can't invite yourself. and Already invited or this person is already a member. Inviting teammates walks through the flow.

Accepting an invitation#

The link opens a page headed Accept invite with the copy "Enter the email this invite was sent to, and we'll add you to the workspace." Enter the invited address and press Accept invite. On success the page confirms: Accepted. You now have access to <owner>'s workspace.

Two things to know. Invite links do not expire, so an old one still works. And accepting requires only the token and the matching email address, so treat an invite link as a credential and do not post it anywhere public.

Switching between workspaces#

Once you belong to more than one, the Team screen lists them under Workspaces You've Joined. Each row offers Switch →. Choosing it asks for confirmation:

Switch to <owner>'s workspace? The page will reload.

The page reloads and the banner at the top of the Team screen updates to show which context you are in. Switching is instant and reversible; your own workspace is always one switch away.

Roles, and what they actually control#

There are two role fields on a membership, and only one of them has teeth.

• Blog role (Author, Editor, Owner) is enforced. It governs Blog Studio only: who may write, who may publish or delete, who may manage categories, media and settings. A blocked action returns Your blog role does not allow this action (<capability>).
• Workspace role is displayed as a badge on the member row but does not restrict anything today. Every accepted member has the same access to the workspace data listed above.

Do not rely on the workspace role badge as a permission boundary. If a person should not see the workspace's monitoring and reports, do not invite them. Roles and what each can do is the full matrix.

Removing someone#

On the member's row, press Remove. You are asked to confirm with Remove this teammate from your workspace? and the destructive Remove button. The membership row is deleted immediately and the seat is freed. The person keeps their own account and their own saved work; only their access to your workspace ends. Removing a member covers the detail.

Client workspaces#

Agencies usually want one workspace per client so that reports, alerts and monitoring do not mix. In Metric Vault that is achieved with the same mechanism: the client owns a workspace, invites you into it, and you switch between them. There is no separate object type and no per-client billing surface.

The plan comparison lists a number of client workspaces per tier. Treat those as commercial guidance rather than a hard technical stop, because the product does not count them. Client workspaces explains the practical setup, and Team and workspace billing covers who is billed.

What breaks if you get this wrong#

• Expecting a joined member to spend from their own plan. They do not. While switched into your workspace, their runs draw on your shared credits, so size the plan for the whole team's usage rather than one seat.
• Choosing Owner — full access in the invite dropdown. The invitation is rejected outright. Choose Editor if you want a near-full collaborator.
• Sharing an invite link publicly. Anyone who knows the invited address can accept it, and the link never expires.
• Assuming the workspace role restricts access. It does not. Invitation is the access decision.