Person mailboxes

An owner can give any person in the enterprise an address. Its mailbox is that person's alone: they read it, answer it and file it in the portal, from their own agent, or from code, and nothing they send waits for approval.

Giving and withdrawing an address

An owner gives a person an email address on People: each person's entry shows their address, or No mailbox address. Give one asks for the address, Change moves them to another, and Withdraw takes it away. The address has to be on a domain the enterprise receives mail on, its own mail host or an attached domain whose ownership has checked (Addresses and domains), and nobody else in the product can already hold it: not a member, not an extra address, not another person.

  • Withdrawn, the address is free. Mail to it stops being delivered, and what was kept stays the person's until the plan's mail retention removes it.
  • Removing a person from the enterprise withdraws their address and their extra addresses, and removes their contacts and their signature.
  • Until an owner has given you an address, you cannot send.

Privacy

The mailbox is the person's. Nobody else reads it: not an owner, not a member, not a member's run, and not an API token, which belongs to the enterprise and to nobody, so it is refused the mail scope and the mail routes. A person's contacts and signature are as private as their mail.

Extra addresses

Under the person's address on People, an owner adds further addresses that deliver to the same mailbox, as a member's extra addresses do: exact ([email protected]), with a plus tag, or a domain's catch-all. Each says whether a reply to mail that arrived at it goes out from it (the default) or from the person's own address. An address somebody else already holds is refused. Each extra address can carry a signature of its own (Writing mail).

Through the API, an owner gives or changes an address with PUT /v1/users/:id/mailbox ({ "address": "…" }) and withdraws it with DELETE /v1/users/:id/mailbox; both answer with the person's row. GET /v1/users lists each person's address, and GET /v1/auth/me carries your own as mailAddress. A person's extra addresses are GET /v1/users/:id/mail-aliases, added with POST ({ "address": "…", "replyFromAlias"?: true }), changed with PATCH /v1/users/:id/mail-aliases/:aliasId and removed with DELETE on the same path. Only an owner, signed in, calls these.

Your own inbox

Once you have an address, Inbox sits under Chat in the portal's navigation, with a count of the mail you have not opened yet; the enterprise picker shows the same count on each company where you have an address. It is a mailbox like a member's: inbox, one tab per label, the archive and Sent, each mail opening as its sender laid it out, with its files, the rest of its conversation and its ids, and Open full screen for a page of its own.

On a mail: Reply, Reply all, Forward, Archive or Move to inbox, Labels, Snooze, Move, which hands the mail and its conversation to another mailbox in the company, and Delete, which removes it for good. Above the list, New mail sends from your address. A reply, forward or new mail can leave from one of your extra addresses instead. The inbox takes in a day what your plan allows, as a member's does (Member mailboxes).

Reading and answering from outside the portal

You can read and answer your mailbox as yourself from Claude, ChatGPT or any MCP client, by connecting the enterprise's MCP server and choosing what the app may do with mail when you connect it, or from code with the API. Read lets the app list and read your mail and its files; Write lets it reply, forward, send, delete and file. See Mail over MCP and the API.

Your own mail needs no approval. A member's send waits for the owner to approve the exact message; yours leaves in the call that asked for it. The rules every send meets still hold: it goes out only from an address of yours, the domain has to be one Zero Human sends from, and the sent copy is filed in your mailbox, a reply in the thread of the mail it answers.

Filing your mail

Write access lets an app keep your inbox in order, as a member's triage task keeps a member's:

  • Labels of your own choosing on a message, which the inbox shows as tabs and the list filters by.
  • A handled state: unhandled, replied, skipped, or snoozed until a date and time, after which it is unhandled again. Escalated is a member's state, raised to the owner; your mail has nobody to raise to, so it is refused.
  • Many at once: one change on up to 200 messages by id, or on every unhandled message from one sender.

One-click buttons, on a cadence of your own

A task can declare a button for a mailbox: your inbox offers every such task of the enterprise above its list, or on each open mail, and pressing one starts the task over your mailbox. A template in the Catalog that declares a button is offered too, and pressing it asks to clone the template first. Beside each button over the whole inbox you pick how often it runs for you: By hand, or a cadence such as Every 15 minutes, in the enterprise's timezone. Each time it comes round the OS presses the button for you, recorded as asked for by you. Nobody else can put your mailbox on a cadence.

A token of your own

For a script, a scheduled job or a client that cannot sign in, Account issues a token that is yours alone: name it, choose Read or Read and write, and copy it once. It reaches your mailbox and nothing else, and stops the moment you revoke it or leave the enterprise. The details are on Mail over MCP and the API.

Mail app passwords

For a standard mail app, Account makes app passwords: name one, choose Read only or Read and send, and copy it once. Nobody but you can list, make or revoke them, an owner included. They stop when you revoke them, when your address is withdrawn or changed, and when you leave the enterprise. Over the API, signed in: GET /v1/mail/app-passwords, POST /v1/mail/app-passwords ({ "name": "…", "scope": "read" }, or "read_send") and DELETE /v1/mail/app-passwords/:id. Signing a mail app in with one, over IMAP and SMTP, is still being built: Connect a mail app explains what is coming.