Team and profiles

One account, several people: who administers Mailer and who only reads — managed in Quathos Account.

One account, several people

Your Mailer account belongs to your Quathos organization. Everyone in it signs in with their own Quathos account — there is no Mailer password — and every action in the audit trail carries who did it.

Mailer keeps no user list of its own. Teammates are invited to the organization in Quathos, and the administrator of your organization decides who uses Mailer, and with which profile, in Quathos Account under Product access. Removing someone there removes their access here within seconds.

The two profiles

ProfileWhat they do
administratorRuns Mailer: sends, manages campaigns, contacts, templates, domains, webhooks, projects, API tokens and reads the audit trail.
viewerReads: messages, events, analytics and usage. Cannot send, change or create anything.
Paying for Mailer, and giving or removing profiles, happens in Quathos Account, by the administrators of your organization.

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 profile, so what you read here is what happens.

administratorviewer
Send email✓–
Read messages and events✓✓
Create and run campaigns✓–
Manage contacts and lists✓–
Manage templates✓–
Manage sending domains✓–
Manage webhooks✓–
Create API tokens and projects✓–
Read the audit trail✓–
View usage✓✓
A token never has more power than the person who created it: a viewer cannot mint a sending token, and a sending token is still limited to sending. See Authentication.