Client Workspaces
One workspace per client in RankX AI. What a workspace holds, how the Website pool works, and what happens when you remove one.
A Client Workspace is one client business inside your agency. It holds that client's Websites, its visibility permissions, its credit ceiling, its branded reports and the users you invite from that client.
It is the unit you report on, bill against and share. Almost everything on the agency track is scoped to one.
What a workspace holds
| Held per workspace | Notes |
|---|---|
| Websites | Drawn from the agency's shared pool |
| Visibility permissions | Seven switches deciding which sections that client sees |
| A credit ceiling | Optional. Uncapped by default |
| Agency Client users | External portal users for this client only |
| Report schedules | Monthly, with recipients |
Everything measured for a Website belongs to the workspace that Website sits in: prompts, keywords, audits, content and history.
The pool, and the count
Two different limits, and mixing them up is the most common misreading of an agency plan:
Websites are pooled across the whole agency. A plan allowing fifty lets you distribute them however you like, and moving one client's Website to another does not need a plan change.
Client Workspaces are counted. That number is how many distinct clients you can run at once, and hitting it means adding another is refused.
Both are in plans and limits.
Your own workspace
Every agency has one primary workspace of its own, and it is not a client. It holds your own Websites, and it is treated differently in exactly one place: an agency's own work is never capped by a client budget.
Creating one
Create the workspace, then add Websites to it. Each Website goes through the same onboarding as any other, and the free onboarding package rules apply per root domain rather than per workspace, so a client whose domain has been onboarded before does not receive a second free package.
That is worth knowing when you take over a client from another agency who also used RankX AI: the entitlement is spent, and it is spent on the domain.
Deciding what a client sees, before you invite them
Set the visibility permissions before the first Agency Client user logs in, because the safe direction is one-way.
An absent permission means allowed. So a client account created before a permission existed keeps seeing everything it saw, and an agency switches a section off rather than switching the rest on. That is deliberate: a permission added in future cannot silently take a section away from a client who is already using it.
The consequence for you: a workspace you have not configured shows the client everything. See what clients can see.
Moving a Website between workspaces
Websites are pooled, so moving one is a reassignment rather than a rebuild. Its history goes with it.
Two things move with it that are worth thinking about first: it becomes visible to the destination workspace's Agency Client users, and its spend begins counting against the destination's ceiling rather than the origin's.
Removing a workspace
Removing a Client Workspace removes what belongs to it, including its Websites' measurement history and any credentials scoped to it. It is not a soft archive.
Two safer alternatives, depending on what you actually want:
To stop a client spending, set its allocation to zero rather than removing the workspace. That stops all spend for that client immediately and is reversible.
To stop a client seeing anything, remove the Agency Client users from it. The data stays, your team keeps access, and nothing is destroyed.
Take an export of anything you need before removing a workspace for real.
Where to go next
- Roles and permissions, for who can do what.
- What clients can see, before inviting anyone.
- Per-client credit budgets, for the ceiling.
Running an agency
How the RankX AI agency track is organised. Client Workspaces, roles, the seven visibility permissions, per-client budgets, white label and the client portal.
Roles and permissions
The four RankX AI roles, what each can do, why only one can approve an MCP connection, and why Agency Clients do not consume seats.