Teams
One account, many users. The owner and admins manage the account; members work the inbox.
Roles
| Role | Can |
|---|---|
admin | Everything: keys, billing, webhooks, numbers, team, plus all member abilities. |
member | Inbox, contacts, broadcasts, templates, messaging. |
viewer | Read-only: sees everything a member sees (inbox, messages, contacts, deliverability, usage, spend), changes nothing. |
Admin-only routes return 403 to members and viewers; any change a viewer
attempts returns 403. Admins change roles from Console → Team, and every
invite, role change, and removal is recorded in the audit log.
Invites
Console → Settings → Team → enter an email, pick a role, and select Invite. We email the person a link; it is single-use, expires after 7 days, and only the invited address can accept it. They sign in (Google, GitHub, or email) with that address and land on your team. An account that already belongs to another team must use a different sign-in.
Pending invitations are listed with the members. From the … menu an admin
can resend the email, copy the link, or revoke the invitation.
Managing members
From the … menu next to a member, an admin can change their role or remove
them. Anyone except the owner can leave the team from the same menu next to
their own name.
Signatures
Each user can set a signature (Console → Team → your profile); it is appended to messages they compose in the console.