Team roles
What owners, admins, developers and marketing members can each do.
Every member of a team has one of four roles. Anyone on the team can read everything the dashboard shows; a role decides who can change what.
| Role | What it is for |
|---|---|
| Owner | Everything, including deleting the team and handing the owner role on. A team always keeps at least one owner. |
| Admin | Everything except deleting the team and the owner role. |
| Developer | API keys, webhooks, domains, SMTP credentials, MCP and inboxes. |
| Marketing | Broadcasts, contacts, segments, topics and list verification. |
Who can do what
| Action | Owner | Admin | Developer | Marketing |
|---|---|---|---|---|
| Billing and plan | ✓ | ✓ | ||
| Invite members, change roles, remove members | ✓ | ✓ | ||
| Team settings, brand defaults, audit log | ✓ | ✓ | ||
| Notification addresses for owner notices | ✓ | |||
| Delete the team | ✓ | |||
| API keys, webhooks (including the signing secret) | ✓ | ✓ | ✓ | |
| Domains: add, verify, change tracking and unsubscribe settings, delete | ✓ | ✓ | ✓ | |
| SMTP credentials, MCP agent keys and tool switches | ✓ | ✓ | ✓ | |
| Create, change and delete inboxes and their safety rules | ✓ | ✓ | ✓ | |
| Request and response bodies in the request log | ✓ | ✓ | ✓ | |
| Create, edit, send and cancel broadcasts | ✓ | ✓ | ✓ | |
| Add, edit and delete contacts; segments and topics | ✓ | ✓ | ✓ | |
| Add an unsubscribe by hand, verify a list | ✓ | ✓ | ✓ | |
| Take back an unsubscribe, remove a suppression, erase a recipient | ✓ | ✓ | ||
| Templates, sending an email, working a received message or an inbox (replies, drafts, threads, labels) | ✓ | ✓ | ✓ | ✓ |
CSV exports follow the same lines: contacts, broadcast recipients and unsubscribes for marketing; domains, API keys and request logs for developers; sent emails, suppressions and the audit log for owners and admins.
Where a role applies
- Dashboard — controls a role cannot use are hidden or disabled, and the server refuses the action anyway.
- MCP — a connected app acts with the role of the person who connected it, checked on every call. See MCP.
- API keys — a key acts with the role its creator has today, checked on every request. A full-access key does every everyday operation (sending, contacts, segments, topics, broadcasts, domains, webhooks, keys) whichever role the creator has; a key limited to one domain does not reach webhooks, suppressions, templates or the team’s other keys (see API keys). Erasing a recipient, removing a suppression and taking back an unsubscribe need a key whose creator is an owner or admin right now; any other key answers
403 forbiddenfor those, and a key made through the API carries the creator of the key that made it. A send-only key can only send. When the creator is removed from the team or leaves, their API keys and agent keys stop working at once.
Invitations carry a role; the invited person gets it when they accept. Owners and admins change it later under Settings → Members.