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.
The agency track adds a client dimension to everything RankX AI does. Each client business gets its own Client Workspace holding its own Websites, with its own visibility permissions, its own spending ceiling, its own branded reports and its own portal to log into.
Measurement is identical on both tracks. What the agency track adds is structure around who sees what, who spends what, and whose brand is on it.
The pieces
| Piece | What it does |
|---|---|
| Client Workspaces | One workspace per client, holding that client's Websites |
| Roles and permissions | Agency Owner, Agency Admin, Member and Agency Client, and what each can do |
| What clients can see | Seven per-workspace switches deciding which sections a client sees |
| Per-client credit budgets | A ceiling on the shared wallet, per client |
| White label | Your domain, logo, colours and sending address |
| Client reports | Scheduled monthly reports with a written narrative |
| The client portal | Where a client logs in |
Websites are pooled, workspaces are counted
Two limits with different shapes, and mixing them up is the most common misreading of an agency plan:
Websites are a pool across the whole agency. A plan allowing fifty Websites lets you put them wherever you like: forty on one client and one each on ten others is fine.
Client Workspaces are counted separately, and that count is the number of distinct clients you can run.
Both are in plans and limits.
One wallet, with per-client ceilings
There is one credit wallet per agency. Client budgets are a ceiling on that wallet, not a sub-wallet: no credits are moved and none are set aside.
The consequence catches people out, so it is worth stating before you meet it: the agency wallet can be full while one client is stopped. Topping up changes nothing for that client until the allocation is raised.
The default is uncapped, so the feature is a no-op until you set a number. See per-client credit budgets.
Agency Clients do not consume staff seats
Your plan's seat limit counts your team. An Agency Client is an external portal user for one workspace, and they do not count against it.
So inviting a client's marketing manager to see their own dashboard costs you nothing, which is the behaviour you want from a feature whose whole purpose is to be used.
Your own workspace is not a client
Every agency has one primary workspace of its own, and RankX AI treats it differently in the one place it matters: an agency's own work is never capped by a client budget. An agency is not a client of itself.
What is out of scope here
Super Admin is staff-only and cross-tenant, and is deliberately not documented in customer-facing docs.
Top-up purchase is not open yet. The packs and prices are final and the checkout is not live, which is stated in credits and billing rather than left for you to discover when you need credits.
Where to go next
- Client Workspaces, the unit everything else hangs off.
- What clients can see, before you invite anyone.
- Per-client credit budgets, before you set one.