Team & Roles
Every member of a workspace has one role: Owner, Admin or Member.
What only an owner or admin can do
Members can run the day-to-day work: leads, campaigns, the inbox and tags. These actions need an owner or admin:
| Area | Action | API |
|---|---|---|
| Leads | Export every lead as CSV | GET /reports/leads.csv |
| Leads | Bulk-delete leads | POST /leads/bulk-delete |
| Campaigns | Delete a campaign (and see what it would remove) | DELETE /campaigns/:id, GET /campaigns/:id/delete-preview |
| Suppression | Block a whole domain | POST /suppression/domain |
| Suppression | Bulk-import blocks | POST /suppression/bulk |
| Suppression | Unblock an entry | DELETE /suppression/:id |
| Tags | Delete a tag | DELETE /tags/:id |
| Mailboxes | Add, import, edit or delete mailboxes, start/stop warmup, test-send, bulk changes | /mailboxes/... |
| Workspace | Webhooks, API keys, team invites, billing, branding |
A member who tries one of these gets 403 with: “Only an owner or admin of this workspace can do
this. Ask one of them, or to change your role.”
An API key acts as the owner of its workspace, so it passes these checks. Billing, team, workspace settings, branding and API keys still refuse any API key. Some actions are stricter through a key: see Deleting a campaign.
Deleting leads
A lead that was already emailed, or that replied, can be deleted. Its replies are deleted with it. The emails sent to it are kept, so mailbox daily limits, plan quota and bounce health stay right.