Custom roles. Resource-level permissions.
Give each teammate access to exactly the campaigns, lists, servers, and domains they need. Lock down the parts of the stack where mistakes cost reputation.
- Roles
- CustomRoles
- Permissions
- Per-resourcePermissions
- Assignment
- Per-workspaceAssignment
- Every change
- AuditEvery change
Outbound is high-blast-radius. Access should match.
A badly configured sending server, a stray campaign, or a mishandled domain can burn reputation that takes months to recover. The default 'everyone is admin' model breaks down the moment the team has more than two people.
Mailers.io ships with custom roles, resource-level permissions, and per-workspace role assignment. Campaign operators run campaigns; infrastructure people touch sending servers and domains; auditors get read-only visibility across the whole workspace.
Design a role. Assign it. Audit it.
- Step 1
Create a role
Define permissions per resource group — campaigns, lists, automations, templates, forms, servers, domains. Full or read-only per group.
- Step 2
Assign to members
Apply roles per workspace. A user can hold Admin on one workspace and Viewer on another.
- Step 3
Audit every change
Role edits, membership changes, and credential events are captured in the audit log with actor and timestamp.
Permissions that map to how outbound teams actually work.
Campaign permissions
Separate who can draft, who can send, and who can only view results.
List & form permissions
Lock subscriber imports and deletions to specific roles; let others view only.
Template permissions
Protect shared templates from accidental edits while letting operators clone and ship.
Sending server permissions
Keep provider credentials, pools, and quotas editable only by infrastructure owners.
Sending domain permissions
Domain changes can only happen via approved roles. DNS verification stays stable.
Scoped API keys
API keys inherit role-like scopes. A marketing integration cannot rotate provider credentials.
Audit log
Actor, timestamp, and diff captured for every sensitive action. Exportable for compliance.
SSO & SCIM (Premium / Enterprise)
SAML and OIDC SSO on Premium; SCIM provisioning on Enterprise. Keep identity centralised.
- You run a team larger than 2 people operating outbound email
- You want campaigns editable without exposing infrastructure
- You need a clean audit trail for internal or customer security reviews
- You want API keys scoped to what they should touch
- Role design is yours; we provide the primitives, not opinions
- SSO/SCIM are plan-gated (Premium / Enterprise)
- Audit logs persist per plan retention windows
Questions answered clearly.
Grow the team. Keep outbound safe.
Custom roles, scoped keys, and a real audit trail — the controls you need to run serious volume with more than one person.