Bring the whole team in. Without giving everyone the master key.
Owner, Admin and Sender roles by default; custom roles you define per workspace, mapped to fine-grained permissions across every resource sendrules ships. Every action captured in an immutable audit trail your compliance team can actually export.
One shared login, and everybody knows the password.
The developer needs to add a webhook. The marketer needs to check yesterday’s open rate. The finance controller needs the invoice. Your ESP has one login per account, so you either share the master credential and hope nobody deletes a provider, or you tell everyone to ask you. Neither is a policy — and neither passes a security review.
sendrules ships with role-based access from the first send. Group people into teams, give each team the permissions they actually need, and audit every mutation so the answer to “who changed the send rule at 3 a.m.?” is a query, not a Slack thread.
Three defaults. Custom roles when you need them.
Fine-grained. Not the two-tier “admin or member” shortcut.
Group people. Assign teams to rules. Rotate members without touching permissions.
Every mutation captured. Every actor named. Nothing gets lost.
SAML SSO, SCIM provisioning, and named-engineer support on the Enterprise tier.
Below Enterprise, password authentication over TLS with optional TOTP is standard on every plan. Enterprise adds SAML single-sign-on with your identity provider (Okta, Azure AD, Google Workspace, Auth0, and any SAML 2.0-compliant IdP), SCIM 2.0 just-in-time provisioning so a de-provisioning event in your IdP removes access everywhere, and a named engineer for the initial rollout so nobody guesses which attribute maps to what.