Team roles and invites, explained
The Mailyte team · · 4 min read
Once more than one person touches your email setup, "everyone is an admin" stops being convenient and starts being a liability. Mailyte's roles exist so that the person who needs to read a delivery log doesn't also hold the button that deletes the domain.
The four roles
- Owner — full access, including billing and deleting the workspace. Every organisation has one.
- Admin — manages domains, mailboxes and members. Cannot touch billing or delete the workspace.
- Developer — API keys, webhooks and SMTP credentials. The role your integrations engineer needs and nothing more.
- Viewer — read-only access to reports and logs. For the person who needs to answer "did that receipt go out?" without being able to change anything.
Mailbox ≠ member
These are two different things, and conflating them is where most email admin goes wrong.
A mailbox is an address that receives mail — sales@yourdomain.com. A member is a person with a login to the Mailyte dashboard. Someone can have one, the other, or both:
- A support agent might have a mailbox and no dashboard login at all.
- A contractor integrating your app might have a Developer login and no mailbox.
You're billed per mailbox. Admin seats and API keys are included, so adding the contractor costs nothing.
Invites, and what happens when someone leaves
Invited members appear as pending until they accept, so you can see at a glance who was invited and never joined. Offboarding removes the login without deleting the mailbox — the address keeps receiving, and its mail stays where it is, which is usually what you want on the day somebody leaves.
Every administrative action is recorded and attributed. Who created that mailbox, who rotated that key, who changed that DNS record — with a name and a timestamp against it.
