Test team invite emails before you ship them
Stand in for the person being invited with a private test inbox, and check the inviter, the workspace, the accept link, and what happens on a second click.
Free plan includes 500 emails a month. No credit card.
- 1Inviter and workspaceNames the right person and team
- 2RoleMatches what they were actually invited as
- 3Accept linkOpens the right environment, single use
- 4ExpiryStated, and enforced on old invites
Why invite emails are hard to test properly
An invite email has more moving parts than most transactional email: an inviter, a role, a workspace, and two different account states.
Real teammates as test data
It is tempting to invite a real coworker to test the flow, but that adds noise to their real inbox and their real account.
Multiple roles to cover
An invite behaves differently for an existing account, a brand-new signup, and someone who declines, and each needs its own test.
Stale invites pile up
A shared test inbox fills up with old invites, making it hard to tell which one is the one you just sent.
How to test a team invite in four steps
The same flow works for a new signup, an existing account, or a declined invite.
- 01
Create an inbox for the invitee
Add an inbox such as [email protected] to stand in for the person being invited.
- 02
Send the invite
Invite that address to a project, workspace, or team from your app as an admin would.
- 03
Watch it arrive live
The invite email appears immediately, with no refreshing needed.
- 04
Accept it, then try again
Follow the accept link to confirm it works, then open the same link again to confirm it is rejected the second time.
What to check in every invite email
Delivery is the easy part, these are the details that break in real products.
Inviter and workspace name
The email clearly states who sent the invite and which team or project it is for.
Accept link destination
Opens the right environment and, ideally, pre-fills the invited email address.
New vs existing account
The flow correctly detects whether the invited address already has an account.
Expiry and resend
An old invite expires, and resending issues a fresh, working link.
Already accepted
Opening an accepted invite a second time fails safely, not with a confusing error.
Role and permissions
The invited member lands with the role they were actually invited as, not a default.
Common team invite bugs
If you see one of these, the flow is not ready to ship.
| Bug | What you will notice |
|---|---|
| Wrong workspace name | The invite email shows a different team than the one that sent it. |
| Link opens production | A staging invite's accept link opens the live site. |
| Double membership | Accepting twice adds the member to the team twice. |
| Silent role downgrade | The invited member joins with a lower role than they were offered. |
| Invite never expires | A months-old invite link still works. |
| Resend does not refresh | Resending an invite keeps sending the same, already-expired link. |
Test team invites with Inceptmail
A private test inbox for every project, built for checking exactly what your app sent, without touching a real coworker's inbox.
One address per test persona
Stand in for the invitee without touching a real coworker's inbox or account.
Live delivery
Invite emails appear the instant they are sent, so you are never guessing if it went out.
Preview and raw HTML
Check the rendered invite and the underlying markup, side by side.
Shared with your team
Give QA teammates access to just the inbox they need to test invite flows.
Also testing magic link logins or signup verification? See every guide in email testing guides.
Team invite email testing FAQ
How do I test a team or workspace invite email?
Create a private test inbox to stand in for the person being invited, send the invite from your app, and inspect the email that arrives. Accept it once to confirm the flow works, then try the same link again to confirm it is rejected.
How do I test invites for both new and existing accounts?
Use one inbox that has no account in your app yet to test the new-user path, and a second inbox with an existing account to test the existing-user path. Both should end with the person as a member of the team.
What should happen when someone opens an already-accepted invite?
It should fail with a clear message, such as this invite has already been used, rather than adding the person again or showing a generic error.
How long should an invite link stay valid?
Many products use anywhere from a few days to a couple of weeks, since invites are often accepted later than a login link. Whatever you choose, test that an expired invite fails safely and that resending issues a working one.
Can I test invites sent by Clerk, WorkOS, or a custom invite system?
Yes. Inceptmail addresses receive mail from anywhere, so it does not matter which service sends the invite, only that it is addressed to your test inbox.
Is Inceptmail free for testing invite emails?
Yes. The Free plan includes 500 emails a month, 3 inboxes per project, and 7 days of message history, with no credit card needed.
Give your test email a proper home.
Create your first inbox in under a minute. The Free plan covers a whole project.
Get started free