"use_case": "For teams"
Shared inboxes for checking flows by hand
Staging needs somewhere for its email to go. Point it at your project and everyone on the team sees every message in the dashboard, with the code or link already pulled out.
Who it's for
- QA and product teams walking through sign-up and onboarding on staging
- Developers checking a new email template before it ships
- Support reproducing what a customer received
- Members of your organization only, invited by an admin
The job
Checking a flow by hand means making a new account again and again. Each one needs a new address, and the email has to land somewhere the whole team can see, not in one person's personal inbox.
- 01Create a project for staging. Invite your team to the organization with a role each.
- 02Use any address. Make one up per test account; every prefix lands in the project.
- 03Read it in the dashboard. New mail appears live, with the HTML, text, headers and links.
- 04Copy the code. Verification codes and links are extracted, so there is nothing to hunt for.
Name addresses so they read well
Every prefix is an inbox, so a naming convention is all the setup there is. Prefer a terminal? receiver watch from the CLI streams new mail as it arrives.
bash
# One project for staging; any prefix works
anna-signup-1[email protected]
[email protected]
support-repro-4821[email protected]
# Stream new mail for the project, or for one address
receiver watch
receiver watch [email protected]Your team only
Project mail is visible to members of your organization, nobody else. Roles decide who can manage keys and settings.
Kept for your plan’s retention
Mail is deleted automatically after 7 to 365 days depending on plan, or by hand from the dashboard.
Same inbox for automation
When a check becomes a test, the API and SDKs read the same project. Nothing to migrate.