Team and seats
A RankX AI seat counts a member of your team. Who counts, how to invite staff and clients, what the seat limit does, and what to check before someone leaves.
A seat in RankX AI counts a member of your team: Agency Owners, Agency Admins and Members. Agency Clients are external users of one Client Workspace, and the seat limit is set for your own team.
Seat limits differ by plan and are listed in plans and limits.
Who counts as a seat?
| Person | Shown in the app as | Counts as staff |
|---|---|---|
| Agency Owner | Owner | Yes. Every account always has at least one |
| Agency Admin | Manager | Yes |
| Member | Member | Yes. Staff who do the work, without the Agency Admin area |
| Agency Client | Client | No. An external user of one Client Workspace |
Client users are kept apart from staff so you can give every client a login without rationing them. See client access for what a client sees when they sign in.
Which actions are reserved for the owner?
The owner role holds the actions that commit the whole account:
- Billing, including plan changes and top-up packs.
- MCP credentials. Issuing a personal access token or approving an OAuth connection creates a credential that can spend credits and change a live website. See MCP authentication.
- Removing people from the team.
RankX AI's database refuses to remove or demote the last owner, so an account always has someone who can pay and manage credentials. A second owner is allowed, and transferring ownership is a deliberate act rather than a side effect of an invitation.
How do I invite someone?
Staff are invited in Settings, then Team, and see what their role allows: every Client Workspace on the Agency track, and everything on a Direct account.
Agency Clients are invited to one Client Workspace from Agency Admin, and see only the sections that workspace permits.
Set a workspace's visibility permissions before inviting its first client user. A permission that has not been set counts as allowed, so an unconfigured workspace shows the client everything in it. See what clients can see.
What happens at the seat limit?
Inviting another staff member is refused, not queued. Free a seat by removing someone who has left, or change to a plan with more seats.
A downgrade never removes anyone. If you are over the new limit, inviting is refused until you are back under.
What happens when someone leaves?
When the owner removes a person, their access ends. Any MCP token or OAuth connection they created stops working on its next request, because RankX AI checks the creator's membership every time a credential is used.
So before you remove the person who set up your integrations, check Settings, then AI Agent Access. It lists every credential with its scopes, client and last use, so you can see what depends on it.
Offboarding checklist
- Note the credentials the person set up in AI Agent Access.
- Reissue anything still needed from an account that will remain.
- Update the AI clients and scripts that use them.
- Remove the person in Settings, then Team.
- Check nothing broke: the last-used times show whether each connection is still in use.
Where to go next
- Roles and permissions, for what each role can do.
- Security, for sessions and sign-out.
- MCP authentication, for credentials and revocation.
Questions
How many seats does each RankX AI plan include?
Seat limits differ by plan and are listed in plans and limits. Agency Scale has no seat limit.
Can a RankX AI account have more than one owner?
Yes. RankX AI requires at least one owner at all times and allows more than one.
Who can invite people to RankX AI?
The account owner and Agency Admins (shown as Manager) manage the team in Settings, then Team. Only the owner can remove someone.
Last updated