Roles and permissions
RankX AI has four roles. Agency Owner, Agency Admin and Member are your staff; an Agency Client sees one workspace and cannot spend credits or change settings.
RankX AI has four roles. Three are your team and one is your client, and that split is the boundary everything on this page rests on.
Agency Owner holds billing and is the only role that can issue MCP credentials. Agency Admin is staff with access to every Client Workspace and to Agency Admin.
Member is staff who do the work: they add Websites, run checks and manage content, and they do not reach Agency Admin. Agency Client is an external user of one Client Workspace.
Most of a team belongs on Member. Choose Agency Admin for someone who will also configure clients, permissions, budgets or white label.
What can each role do?
| Agency Owner | Agency Admin | Member | Agency Client | |
|---|---|---|---|---|
| See Client Workspaces | Every one | Every one | The ones they are assigned to | Only their own |
| Add and delete Websites | Yes | Yes | Yes | No |
| Run checks, audits and research | Yes | Yes | Yes | No |
| Generate and publish content | Yes | Yes | Yes | No |
| Work the Tasks board | Yes | Yes | Yes | Yes, when Tasks is allowed |
| Reach Agency Admin | Yes | Yes | No | No |
| Set client permissions, budgets and reports | Yes | Yes | No | No |
| White label settings | Yes | Yes | No | No |
| Billing, plan and top-ups | Yes | No | No | No |
| Issue an MCP token or approve a connection | Yes | No | No | No |
| Uses a staff seat | Yes | Yes | Yes | No |
Member is a working staff role, not a read-only one. A Member can delete a Website, spend credits and publish to a connected site. What a Member cannot do is configure the agency: clients, permissions, budgets, reports and white label all live in Agency Admin.
Why do only owners handle billing and MCP?
Billing and MCP credentials are the two ways to commit money or capability on the account, so RankX AI keeps both with the Agency Owner.
Billing covers plan changes, payment and top-up packs. MCP credentials cover issuing a personal access token and approving an OAuth connection.
Either one creates a credential that can spend credits and edit a live website, and its scopes are fixed when it is issued. See MCP authentication.
Can an agency lose its owner?
No. Only an Agency Owner can remove a team member, and an owner cannot remove themselves or another owner. The database also refuses to remove the last Agency Owner, so an agency always has someone who can pay and issue credentials.
What can an Agency Client do?
An Agency Client reads the sections their workspace allows and works the Tasks board. They can also propose Brand Book entries, which start as drafts for your team to approve.
An Agency Client cannot:
- See any other workspace, or that other clients exist.
- Run checks, generate content or spend credits.
- Connect or disconnect integrations, or change settings that belong to the agency.
- See billing, the credit balance or your team.
Every hidden section is also guarded on the server, so typing its address directly is refused rather than served.
Do Agency Clients use staff seats?
No. Your plan's seat limit counts staff: Agency Owners, Agency Admins and Members. Inviting an Agency Client never needs a free staff seat, so inviting a client's marketing manager costs you nothing.
How do client permissions relate to roles?
Roles decide what a person can do. Client permissions decide which sections an Agency Client sees in one workspace, and they never filter your own staff.
Each Client Workspace carries nine switches. See what clients can see.
How do I invite people?
Staff are invited from Settings, then Team, as an Agency Admin or a Member, by an Agency Owner or an Agency Admin. Agency Clients are invited to one Client Workspace from that client's Access tab in Agency Admin.
Set the workspace's permissions before you invite a client, because an absent permission means allowed and an unconfigured workspace shows the client every section a client login can reach.
What happens when I remove someone?
An Agency Owner removes staff from Settings, then Team. Removing a person ends their access on their next request rather than at a later sweep. It also ends the MCP tokens and connections they created, so check who set up your integrations before you remove them.
Where to go next
- What clients can see, for the nine permissions.
- Client logins, for what an Agency Client actually gets.
- Team and seats, for the seat limits.
Questions
Can a Member see the Agency Admin area?
No. A Member does the work, including running checks, spending credits and publishing, but Agency Admin is for Agency Owners and Agency Admins only.
Can I invite someone as an Agency Owner?
No. Owners and Agency Admins invite staff as Agency Admin or Member. The Agency Owner role belongs to the person who created the account.
What happens to MCP tokens when someone leaves?
They stop working. RankX AI checks on every request that the person who created a token or approved a connection is still a member, so removing the person ends their credentials. See MCP authentication.
Last updated