Give people the access their job needs
Every member has one of four roles, every key can be limited to what it must do, and every change to your team is written to a log nobody can edit.
What Team and security does
Four roles
Owner does everything, admin everything except deleting the team, developer handles API keys, webhooks, domains and inboxes, and marketing handles broadcasts and audience. The server enforces the role, not only the dashboard.
Two-factor sign-in
A 6-digit code from an authenticator app, ten one-time backup codes and the option to trust a browser for 30 days. It belongs to your account, so it covers every team you are in and the sign-in that connects an MCP client.
Keys that can only do one thing
Create a sending-only key for your app, limit it to one verified domain, or limit a full-access key to a single inbox for an AI agent. A leaked sending-only key cannot read contacts or create other keys.
Risky acts stay with owners and admins
Erasing a recipient, removing a suppression and taking back an unsubscribe need an owner or admin, whether done in the dashboard, over MCP or with an API key.
An audit log that cannot be edited
Owners and admins see who did what, to what, from which address and when: keys, domains, webhooks, members, sign-in security, inboxes and billing. Rows hold no secrets or message content, and you can export them as CSV.
Where to set it up
Invite members and set roles under Settings → Members. Turn on two-factor under Settings → General, in Your account. Create keys under API keys, where you choose the permission, a domain and an inbox. The audit log is under Settings → Audit log.