The four roles
| Role | What it can do | Costs a seat? |
|---|---|---|
| Owner | Everything. Manages members, billing, API keys, can delete the org. | Yes |
| Admin | Manages members, projects, and org API keys. Everything except deleting the org. | Yes |
| Member | Works on the projects you assign. Manager access on a project means edit, viewer means read-only. | Only with manager access on at least one project |
| Client | Read-only login for your client. Scoped to the projects you pick, usually one. | Never. Free and unlimited |
Per-project access
Owners and admins see every project in the org. Members start with zero. Each project assignment grants exactly one project at one of two levels:- Manager: full edit. Run prompts, edit brands and topics, change settings.
- Viewer: read-only. Dashboards, topic performance, reports. No edits.
- Owner invites Sarah as a member, assigned to Acme as manager and Beta as viewer.
- Sarah signs in and sees exactly two projects.
- On Acme she runs prompts, edits competitors, changes the schedule. On Beta she can look but never touch.
- Gamma never appears in her sidebar. She has no way to know it exists.
Where you manage all this
- Team (in the sidebar, owners and admins only): invite teammates and clients, manage roles, see the full roster.
- Access (per project, owners and admins only): add or remove members on the project you have open, flip manager vs viewer.
- Usage (owners, admins, and members): the org’s credit pool, per-project and per-member usage, and the named seat list.
Teams and seats
Inviting teammates, what costs a seat, and what happens at the cap.
Client logins
Give every client a live dashboard instead of a monthly PDF.
API keys and MCP
Org-scoped service keys that survive employee turnover.