Member mailboxes
Every member has a mailbox at its own address. Its tasks read, file and answer it, every send waits for approval, and the enterprise owner can work it by hand in the portal.
The inbox
Every member receives mail at its address, at a plus-tagged form of it such as [email protected],
and at any extra address an owner gives it (Addresses and domains). This is how
a member gets on with the outside world: signing up for an account in its own name, receiving the confirmation code,
accepting an invitation. See GitHub for a member joining GitHub with its own address. An
address is an identity, not an account anywhere else: a member gets an account in another system only when someone
creates one for it there.
Inbox, on the member's page in the portal, lists what has arrived, newest first, with unread mail marked. Opening a message marks it read. A message sent as HTML shows as its sender laid it out, styles, tables and images included, remote images too, so opening it can tell the sender it was opened. It is shown in a frame of its own where nothing in the mail runs, and links open in a new tab. An open message shows its attachments, the rest of its conversation (what arrived and what the member sent back), and its ids: the Mail ID a task or tool names it by, its Message-ID and its conversation. Open full screen gives it a page of its own.
Tabs and labels
The mailbox is shown in tabs, and each count is for the whole mailbox:
- Inbox is open mail that no task has labelled yet.
- A tab per label is open mail carrying that label. Labels are whatever the member's tasks give a message; the OS has no fixed list, and a label with no open mail has no tab.
- Archive is everything closed that arrived, whatever its label: mail that was answered, and mail a task left on purpose.
- Sent is everything the member sent: its tasks' replies and new mail, and the owner's.
- Contacts and Signature, for the owner, are on Writing mail.
Handled, snoozed and archived
Each message has a handled state. It is open while it is unhandled, waiting on a decision, or snoozed until a date
and time, after which it is unhandled again. It is closed once it is replied to or skipped. When a decision about a message is rejected, times out or its run is cancelled, the OS closes the
message, so it moves to Archive instead of staying under its label. A task records what it decided with
os.mail_set_label and os.mail_set_handled, or about many messages at once with os.mail_set_many
(Mail in tasks).
Spam
Mail that reaches Zero Human through its own receiving servers, as an attached domain's mail does, is scored for spam on the way in. A message scored as spam is marked Spam in the list and when open, with its score, and a task reads the same score and flag on the message. A message scored far beyond that is refused at the door and never stored. Mail that was not scored shows no mark. See Safety and deliverability.
Inbound mail a day
Your plan caps how much inbound mail one mailbox takes in a day: 20 messages on Free and 100 on Starter. Company, Scale and Enterprise have no daily cap. The day is the UTC day, so the count starts again at midnight UTC. Only mail stored in that mailbox counts, not another mailbox's and not its own sent copies, and a message delivered twice is counted once.
Mail past the cap that day is held, not lost. The OS keeps each such message as a hold, apart from the mailbox, so neither the member nor its tasks see it yet, and it counts towards your storage. The OS releases held mail by itself, oldest first: into each later day's room up to the cap, or all at once when the enterprise moves to a plan with a higher cap or none. Billing shows the mail taken today against the cap, and how many messages are held. A held message still not released when your plan's mail retention has passed is deleted, as stored mail is.
Mailbox buttons and their schedules
A task that declares a mailbox button (mailboxAction, Tasks over the API) and runs as a role the
member holds is offered above the member's list, or on each open mail, as a one-click button that starts it: the run
reads this mailbox as the member's tasks always do, with the open mail's id for a button on one mail. A button over
the whole mailbox can also run on a schedule: the task's own schedule (Schedules and webhooks)
starts it as a run of the member, over the member's mailbox, exactly as pressing it would. GET /v1/members/{id}/mailbox-actions, and os.member_mailbox_actions over the
MCP server, list the buttons; a task is started with POST /v1/tasks/{id}/runs or os.start_task.
Working the mailbox by hand
The enterprise owner can work a member's mailbox as a mail client: Reply, Reply all, Forward, Archive or Move to inbox, Labels, Snooze and Delete on a message, and New mail above the list. Move hands a mail and the rest of its conversation to another mailbox in the company, another member's or a person's, your own Inbox included, so you can answer it as yourself. How a mail is written is on Writing mail.
Anybody else reads the mailbox only, whatever their grant, and an API token or a connected app cannot act on it.
How sending from a member is approved
A member's tasks send with os.mail_reply and os.mail_send, and every send waits for approval on the exact message
first: the approval card shows the mail as it will leave, signature and quoted text included, and approving it sends
that and nothing more. A rejected or expired approval sends nothing. A reply goes out from the address the message it
answers arrived at, and threads under it, so the person reading it sees one conversation; the sent copy is filed in
the mailbox and listed under Sent. A run can only ever send from an address that delivers to its own member's mailbox.
What the owner sends from the mailbox by hand leaves at once, as the member: the owner is who approves a member's sends, so nothing waits for one. See Gates and tool scopes for how approvals work.