Appearance
Teams
A team is the top-level workspace in SendGrail. Every domain, API key, webhook, email and suppression belongs to a team. A single user (one email) can belong to many teams and switch between them from the dashboard.
When you sign up, SendGrail creates your first team automatically and makes you its Admin.
Roles
There are three roles:
| Role | Can |
|---|---|
| Member | Full access to the team's resources — send emails, create/edit/delete API keys, domains, webhooks and suppressions, view all logs. The one exception is a mailbox given to a particular person, which only they and Admins can open. |
| Mailbox | Signs in to the mail app and nothing else: reads and writes the mailboxes given to them. No domains, no sending, no API keys, no team settings. |
| Admin | Everything a Member can, plus invite users, change member roles, edit team settings, and delete the team. |
The split is intentional: everyone on the team has equal power over sending, only team membership itself is admin-restricted. If you need a read-only collaborator, don't invite them as a Member — they will be able to revoke keys and delete domains.
Inviting teammates
In the dashboard, go to Settings → Team → Invite. Enter an email address and choose Admin, Member or Mailbox. For a Member or Mailbox invitation you can also tick the mailboxes to give them; a Mailbox member needs at least one. The invitee gets an email with a one-click accept link, and the mailboxes become theirs when they accept.
To change which mailboxes someone holds later, click ⋮ on their row and choose Mailbox access.
- The link is valid for 7 days. After that you can resend it from the pending-invitations row.
- An invitee who already has an account signs in with the email the invitation was sent to. If they're signed in as a different address, they're prompted to switch accounts.
- An invitee without an account creates one right on the invitation page (name and password). SendGrail is invite-only, so this is the only way in without an admin creating the account. The address is fixed to the one invited and counts as verified, since the link reached that inbox. Accounts made this way work inside the teams that invite them but can't create a team of their own.
- Once accepted, the invitee is added to the team with the role you picked and the team becomes their current team automatically.
Switching between teams
The team switcher lives at the top of the sidebar — your current team's name with a chevron next to it. Clicking it opens a dropdown listing every team you belong to (the current one is ticked), and the page reloads against whichever team you pick.
Each user's "current team" is remembered between sessions.
In the mail app the switcher sits at the foot of the folder rail, above Mailbox settings, whenever you belong to more than one team. Each team shows your role in it. That is how someone who was given a mailbox in another team gets back to their own: accepting the invitation switches you into the team that sent it, and you switch back from there.
Creating another team
The same dropdown has a + Create Team action at the bottom. It opens a small dialog asking for a team name; on submit you become the new team's Admin and it becomes your current team straight away — useful for spinning up a "Staging" team alongside "Production", or a side project alongside a day-job team.
Managing members
From Settings → Team → Members, an Admin can:
- Change a member's role between Admin and Member.
- Remove a member from the team.
- Cancel a pending invitation before it's accepted.
- Resend an invitation to refresh the token and the 7-day expiry.
A team must always keep at least one Admin — the dashboard refuses any change that would leave it admin-less.
Deleting a team
Settings → Team → Delete team permanently removes the team and everything it owns — domains, API keys, emails, webhooks, suppressions. The action is unrecoverable; the dashboard requires you to type the team's name to confirm.
Team members aren't deleted as users — they stay signed in and switch to another team they belong to (if any).
What resources belong to which team
Anything tied to "your account" actually lives at the team level:
- API keys — see API keys & authentication
- Domains — see Domains & verification
- Webhooks — see Webhooks
- Suppressions — see Suppressions
- Sent emails and request logs
That means: an API key sends from its team's domains, against its team's suppression list, and posts to its team's webhooks. Switching teams in the dashboard changes what you see for all of the above.
Frequently asked
How do I share an API key with the rest of my team?
You don't need to — every Admin or Member of the team can already create and use keys for that team from API keys.
Can the same email address be in two teams?
Yes. The user signs in once and switches between teams from the topbar.
Do my team's reputation metrics carry over if I leave or get removed?
Reputation is per-account, so leaving a team doesn't affect your sending history elsewhere. The team's domains and sending history stay with the team.