Team collaboration
By default, a MailInApp account is you alone. If more than one person needs to work on your projects, invite them under Settings → Team — no separate accounts to provision, no shared logins.
Roles
- Editor — full access to projects, the studio, contacts, sends, schedules and responses. Can't rotate credentials or manage billing/team.
- Viewer — read-only everywhere: can open and review projects, contacts and responses, but every write is rejected.
Only the account owner can invite, change a role, or remove someone — team management itself, like credential rotation, always stays owner-only.
What stays owner-only
A handful of things are gated to the owner specifically, even for an editor with otherwise-full access, because they're credentials or account-level settings rather than project data:
- SMTP relay settings and the native-sending domain
- Stripe Connect (connecting or disconnecting the payments account)
- Minting or revoking transactional Send API keys
- A contact list's push-API key
- A project's webhook signing secret
- Team management itself (invites, roles, removal)
Everything else — building in the studio, managing contacts, sending, reading responses — is identical for an owner and an editor.
Inviting someone
Enter their email and pick a role, then Invite. They get an email with a link to accept; if your SMTP relay isn't configured yet (or the send fails), you're shown the link directly so you can share it another way. Accepting requires signing in — or creating an account — with the exact email address the invite was sent to; the invite itself doesn't grant access to whoever happens to click it.
Once accepted, the person sees your projects, contacts, responses and any private templates you've saved (see Starter templates & your own library) the moment they sign in — there's no account-switcher, since a MailInApp user is either a solo owner or a member of exactly one team.
Nothing changes if you don't use it
Solo accounts behave exactly as before — team collaboration is opt-in, and it doesn't touch existing data, permissions, or how any of the rest of MailInApp works.