Documentation menu

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 a branded invite 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. If they're already a MailInApp user and sign in before checking their email, the invite shows up as a banner on their dashboard too, so it's never something only the inbox knows about.

Once accepted, the person sees that company's projects, contacts, responses, and any private templates you've saved (see Starter templates & your own library) the moment they switch into it.

Belonging to more than one company

Every MailInApp user has their own personal company by default, and can also hold an active membership in any number of other people's companies at once — there's no limit of one. A company switcher in the sidebar lists every company you belong to (your own, plus each team you've accepted an invite into) once there's more than one; picking a different one switches which projects, contacts, plan, and settings you're working against. Nothing in the switcher is visible until you're actually in more than one company — a solo owner or someone with exactly one team sees no extra UI at all.

Each company is independent: its own plan, its own SMTP/domain settings, its own contacts and projects. The account owner can rename their own company from the switcher; team members see whatever name the owner has set.

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.