Working with clients
Team and client access
Roles, seats, and giving a client a read-only view of their own brand.
Seats are unlimited on every plan. Adding a colleague never costs more, because charging per seat pushes agencies to share one login, and a shared login makes an audit trail meaningless.
Roles
| Role | Can |
|---|---|
| Owner | Everything, including billing and cancelling the account |
| Admin | Everything except billing |
| Member | Run scans, manage brands and prompts |
| Client | Read one or more assigned brands. Nothing else. |
The client role
This is the one agencies use most.
A client user sees only the brands you assign them, and can only read. They cannot start a scan, add a prompt, change a competitor, see your other clients, or see anything about your account. They log in, look at their own numbers, and leave.
It is genuinely read-only at the API, not a hidden button in the interface. A client account that tried to start a scan by calling the API directly is refused.
Inviting someone
Team → Invite. They get an email with a link that expires. Invitations are stored hashed, so an invite pulled out of a database is not a usable key.
What a client sees
The brand report as you see it, minus every control:
- Visibility, share of voice, position
- Citations and the citation gap
- Recommendations and the change feed
- Scan history
And a PDF export, which for most agencies is the thing the client actually forwards internally.
Access after a downgrade
Existing team members keep working when a plan changes. Nobody is locked out of an account they were already using because the subscription moved tier. Only adding new resources is gated.