What teammates share

Summary#

Membership shares one thing substantively today: the owner's Blog Studio, at the role you assign. Everything else in each person's dashboard belongs to the account they are signed in as — their credits, their plan, their saved results, their monitoring, their alerts and their reports. Reading this page before you roll a team out will save you the two questions that account for most team support: "why can't my colleague see this?" and "why is my teammate being asked to upgrade?"

Purpose#

Two people working on the same site should not have to duplicate each other's work, and nobody should have to guess whether a report is being sent twice. Membership exists to give a defined group of people a shared place to publish, and to give the workspace owner a single list of who those people are.

The boundary between shared and private is drawn where it is for a practical reason: publishing is genuinely collaborative, while credits and saved work are tied to the person and the plan that paid for them.

Overview#

Once someone accepts your invite, two things become true. They appear in Your Team on your Team screen with an ACTIVE badge, and your workspace appears in their Workspaces You've Joined list with a Switch → action.

From there, one rule explains almost everything:

What membership gives a teammate#

What stays with each account#

How it works#

Membership is a record between two email addresses. Inviting someone creates a pending record between your address and theirs. When they open the link and confirm that address, it becomes accepted. Everything else is checked against that record, so a pending invite grants nothing and a removed member loses access with the click that removed them.

Blog Studio follows membership, not the switcher. When a member opens Blog Studio they are placed on the blog of the workspace they most recently accepted an invite to, with the role recorded on that membership. They do not need to switch workspaces first, and switching does not move them to a different blog. If someone belongs to two workspaces, the most recent acceptance wins.

Credits are metered against the workspace you are working in. When anyone runs a billed tool inside a workspace they have joined, the cost is checked against that owner's plan and drawn from the owner's shared monthly allowance. In your own workspace, runs draw on your own plan. See How credits work for what each tool costs and Quotas and rate limits for how the allowance behaves.

That covers every metered action: the AI tools, the technical SEO tools, the Growth Actions synthesis, image analysis and generation, rank-alert checks, and publishing to a social channel. A post you schedule inside a workspace is charged to that workspace when it goes out, even though it sends hours later, because the account to bill is decided when you press Schedule.

One thing stays with you rather than the workspace: your connected social accounts. A post always goes out on the channels you connected, so joining a workspace does not let you post as its owner. Only the cost moves.

That last point has a consequence worth stating plainly:

When to use membership, and when not to#

Membership is the right tool when several people write for one blog. That is the case it enforces properly: the owner keeps control of settings, editors manage the whole content pipeline, and authors are held to their own posts.

It is the wrong tool for three things. It is not a way to share a credit allowance, because metering is per account. It is not an access-control system, because there is no read-only role and no per-tool permission — see Roles and what each can do. And it is not a way to show a client their dashboard; for that, publish a share link or send a white-labelled export.

What breaks if you get this wrong#

• Duplicate scheduled reports. Two people each create the same schedule on their own account and the recipient gets two emails. Decide who owns a schedule and create it once, on that account.
• Alerts nobody is watching. A member sets up rank alerts expecting the owner to see them. The owner will not. Alerts belong to the account that created them.
• Unexpected upgrade prompts. A member on Free clicks a premium tool inside an Agency owner's team and is told to upgrade. That is the metering rule working as designed.
• The wrong blog. A writer who belongs to two workspaces publishes into the one they joined most recently. Check that before handing over a publishing task.