Teams

On Fleet and above, an account can give some of its addresses to other people: up to 25 on Fleet and 250 on Enterprise, besides you. Members are not charged for. Each member has their own Mailcycle account on any plan, and reads what you share with keys sealed to that account. They never learn your recovery phrase.

Adding someone

1. They open Team in their app and send you their join code. It holds their account id and their account’s public key, never their phrase.
2. You paste it under Team, Add a member. Your app shows six words, a fingerprint of their key.
3. They read out the six words on their own Team page, in person or on a call you trust. Add them only if the words match.
4. Choose the addresses they get, each as read only or read and send.

The words are what stop a server from swapping in a key of its own at the moment someone joins; nothing else can. Your app also pins the key you confirmed, sealed in your vault, and refuses to share anything more if the server ever offers a different one.

What a member can do

Access	Read, mark read, star	Reply and send	Move, delete
Read only	Yes	No	No
Read and send	Yes	Yes	Yes

A member reads a team’s addresses under Team, Teams you’re in, in their own app. Sending from a shared address counts against your plan’s daily limit and your address’s settings; the member’s own hourly limits still apply to them. You see which member sent each message in your audit history. That is the server’s record of who asked, not a signature a client can check.

A member’s API keys do not reach shared addresses, and the SDKs read an account’s own addresses only: shared ones are read in the signed-in app. Nothing is served while your plan does not include teams; it resumes when it does.

Removing someone

Removing a member stops Mailcycle serving them your addresses at once. It cannot take back what they already had: mail they opened, and the keys they were given.

Giving their addresses new keys, so they cannot read future mail even if they get hold of it some other way, is not available yet. When it is, you will choose give their addresses new keys when you remove them: mail arriving from then on is sealed to a new key that only you, the members you keep and your devices are given, and older mail stays readable with the older keys, which are still derived from your phrase.

What the server knows

Mailcycle knows who is in your team, which addresses each member holds, with what access, and when that changed, because it has to in order to serve them. The grants themselves are sealed on your device to each member’s key; the server stores them and cannot open them. It never holds a key to your mail.

See Teams in the API reference.