# Team, roles and seats

> Invite humans to your Trotta Mail organization. Each gets a sign-in and a mailbox of their own. Roles, seats, and why no admin reads a teammate's mailbox.

Source: https://trotta.email/docs/team

Invite the humans you work with. Each gets their own sign-in and their own mailbox. Nobody reads a teammate's mailbox: not a member, not an admin, not the owner.

## Roles

| Role | Runs the organization | Reads |
| --- | --- | --- |
| Owner | Everything, and who is an admin. One per organization; it can be handed over. | Their own mailbox and agent inboxes. |
| Admin | Agent inboxes, keys, webhooks, domains, lists, plan, members. | Their own mailbox and agent inboxes. |
| Member | Nothing. | Their own mailbox. |

A member manages what is theirs: their mailbox, held mail in it, keys limited to it, their password, two-factor and sessions.

## Who reads a mailbox

- A human's mailbox is read by the human it belongs to. For anyone else its ids answer `404`.
- An API key acts for the human who made it. An organization-wide key reaches the agent inboxes and that human's own mailbox, never a teammate's, whatever its scopes.
- A webhook is sent mail from agent inboxes and from its holder's own mailbox only.
- The audit trail shows that a teammate released or discarded mail, not who wrote to them.

## Invite a human

Open [Team](https://trotta.email/console/team) and choose Invite a human. Their mailbox is created at once, on `trotta.email` or on a domain you have verified, and you get a link to send them. The link works once, for seven days. They choose their own password.

```bash
# from the web app's session: an API key cannot manage the team
POST /v1/members
{"name": "Sam Rivera", "local_part": "sam", "domain": "example.com", "role": "member"}
```

Mail that arrives before they join waits in the mailbox, unread by anyone, and is theirs when they do.

Adding a whole team? Choose Add many and upload one file, or let your identity provider do it: see [Add your whole team](https://trotta.email/docs/directory).

## Seats

A seat is a human with a sign-in. An open invitation holds a seat, so a plan cannot be over-invited: 1 on Free, 1 on Developer, 5 on Startup, no limit on Enterprise. Developer and Startup can add seats, $5 a month each. Past the limit, inviting answers `403 seat_limit_reached`. Agent inboxes are not seats.

## Remove a human

Removing someone ends their sessions, revokes the keys they made, deletes the webhooks they hold, and frees the seat. Their mailbox is kept and still receives mail, and belongs to no one: nobody can read it. The owner then gives it to a member, who reads everything in it from then on, or deletes it unread. Both are written to the audit trail.
