The client portal
Where an Agency Client logs in. What they see, what they cannot reach, and what to check before you invite anyone.
The client portal is where an Agency Client, the one role that is not part of your team, logs in to see their own workspace. They see that one workspace, only the sections its permissions allow, in your branding if white label is configured.
They see no other client, and no evidence that another client exists.
What a client gets
The sections their workspace permits, and nothing else. Within those sections they see the same measurements your team sees for their Websites: the same numbers, the same denominators, the same blanks where something was not measured.
There is no separate "client version" of a figure, and that is deliberate. A client reading a lower number than their agency sees is a conversation nobody wants to have.
What a client cannot reach
- Any other Client Workspace.
- Agency settings: billing, team, white label, MCP, integrations at the agency level.
- Any section their workspace has switched off.
The last one is a real boundary rather than a hidden menu item. RankX AI hides the navigation and guards the page, so a client typing the URL directly is refused rather than served. A hidden nav item alone is a convenience, and this product treats it as one.
Before you invite anyone
Four things, in this order:
Set the workspace's permissions
Absent means allowed, so an unconfigured workspace shows the client everything. Switching a section off is the deliberate act. See what clients can see.
Check what is actually in the workspace
Every Website in it is visible to that client. A Website parked there for convenience is a Website your client can see.
Configure white label
Logo, colours and the custom domain, if your plan carries it. First impressions of a portal are mostly branding. See white label.
Look at it yourself
Open the portal as a client would and read it as one. The most common surprise is an empty section: a Google connection that is not ready, or a check cadence that has not produced a second data point yet, both of which look like a broken product to someone who does not know the schedule.
Agency Clients cost you nothing
An Agency Client does not consume a staff seat. Your plan's seat limit counts your own team, so inviting a client's marketing manager, their founder and their web developer costs the same as inviting none of them.
That is deliberate: a portal nobody is allowed to log into is not a feature.
Portal or report?
Both, usually, and they suit different people:
| The portal | A client report | |
|---|---|---|
| Who it suits | Someone who wants to look at the detail | Someone who wants to be told what happened |
| Cadence | Whenever they log in | Monthly, delivered |
| Needs an account | Yes | No, it has a share link |
| Branded | Yes | Yes, with one known exception on the emailed link |
The stakeholder who decides whether to keep paying you is usually in the second column.
Two things to explain to a client once
Both are properties of the product a client will otherwise read as a fault, and explaining them once saves the same conversation every month:
A blank is not a zero. RankX AI shows unknown rather than 0% when nothing has been measured, everywhere. A client who reads a blank as "we have no visibility" has read it backwards. See null is not zero.
Assistants disagree with each other, and with themselves. A per-assistant figure moving between runs is the nature of what is being measured, not a measurement error. The reliable unit is a rate across a panel over time.
Where to go next
- What clients can see, the seven switches.
- White label, for the branding.
- Roles and permissions, for the role boundary underneath.
Client reports
Scheduled monthly reports with a written narrative, delivered by email with a share link. What the narrative costs, and why it degrades rather than blocking.
Plans and limits
Every published RankX AI plan limit, on both tracks, generated from the same source the pricing page renders. What each limit caps, and what it does not.