Team and roles
One account, several people: who pays, who integrates, who sends the campaign and who only reads.
One account, several people
Your account is the company. Everyone who works in it is a member with a role, invited from the dashboard under Users. There is no shared password: each person signs in with their own Quathos Account, and every action in the audit trail carries their name.
The same person can belong to more than one account: an agency running three clients switches between them without three logins. Suspending someone blocks them in this account only.
The five roles
| Role | What they do |
|---|---|
| OWNER | Answers for the account: the only role that manages billing and payment, and the only one that can close it. There is always at least one. |
| ADMIN | Runs the account day to day: users, projects, API tokens, domains, webhooks, the audit trail. No billing. |
| DEVELOPER | Integrates: sends through the API, manages templates, domains, webhooks and API tokens. Does not run campaigns and does not manage people. |
| MARKETER | Sends campaigns: contacts and lists, templates, the campaign itself and its results. No infrastructure credentials, no billing. |
| ANALYST | Reads: messages, events, analytics and usage. Cannot send, change or create anything. |
MARKETER exists so a campaign does not need a developer. The person picks a list, a template and a sender in the dashboard, counts the audience and starts it; domains and API tokens stay with whoever set up the integration. See Campaigns for the lifecycle.
Who can do what
The matrix is generated from the same rules the API enforces. A session in the dashboard and an API token created by that person are capped by the same role, so what you read here is what happens.
| OWNER | ADMIN | DEVELOPER | MARKETER | ANALYST | |
|---|---|---|---|---|---|
| Send email | ✓ | ✓ | ✓ | ✓ | – |
| Read messages and events | ✓ | ✓ | ✓ | ✓ | ✓ |
| Create and run campaigns | ✓ | ✓ | – | ✓ | – |
| Manage contacts and lists | ✓ | ✓ | ✓ | ✓ | – |
| Manage templates | ✓ | ✓ | ✓ | ✓ | – |
| Manage dedicated numbers and senders | ✓ | ✓ | ✓ | – | – |
| Manage webhooks | ✓ | ✓ | ✓ | – | – |
| Create API tokens | ✓ | ✓ | ✓ | – | – |
| Invite and manage users | ✓ | ✓ | – | – | – |
| Read the audit trail | ✓ | ✓ | – | – | – |
| View usage and invoices | ✓ | ✓ | – | – | ✓ |
| Manage billing and payment | ✓ | – | – | – | – |
| Close the account | ✓ | – | – | – | – |
A token never has more power than the person who created it: an analyst cannot mint a sending token, and a sending token created by an owner is still limited to sending. See Authentication.