[{"data":1,"prerenderedAt":37},["ShallowReactive",2],{"$f2wufzrj5k2kh3":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"express":8,"bridge":8,"html":10,"headings":11},"\u002Fdocs\u002Femail\u002Fmember-mailboxes","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.",null,false,[],"\u003Ch2 id=\"the-inbox\">The inbox\u003C\u002Fh2>\n\u003Cp>Every member receives mail at its address, at a plus-tagged form of it such as \u003Ccode>jules+github@northstar.zerohuman.com\u003C\u002Fcode>,\nand at any extra address an owner gives it (\u003Ca href=\"\u002Fdocs\u002Femail\u002Faddresses-and-domains\">Addresses and domains\u003C\u002Fa>). This is how\na member gets on with the outside world: signing up for an account in its own name, receiving the confirmation code,\naccepting an invitation. See \u003Ca href=\"\u002Fdocs\u002Ftools\u002Fgithub\">GitHub\u003C\u002Fa> for a member joining GitHub with its own address. An\naddress is an identity, not an account anywhere else: a member gets an account in another system only when someone\ncreates one for it there.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Inbox\u003C\u002Fstrong>, on the member's page in the portal, lists what has arrived, newest first, with unread mail marked. Opening\na message marks it read. A message sent as HTML shows as its sender laid it out, styles, tables and images included,\nremote images too, so opening it can tell the sender it was opened. It is shown in a frame of its own where nothing in\nthe mail runs, and links open in a new tab. An open message shows its attachments, the rest of its conversation\n(what arrived and what the member sent back), and its ids: the \u003Cstrong>Mail ID\u003C\u002Fstrong> a task or tool names it by, its\n\u003Cstrong>Message-ID\u003C\u002Fstrong> and its conversation. \u003Cstrong>Open full screen\u003C\u002Fstrong> gives it a page of its own.\u003C\u002Fp>\n\u003Ch2 id=\"tabs-and-labels\">Tabs and labels\u003C\u002Fh2>\n\u003Cp>The mailbox is shown in tabs, and each count is for the whole mailbox:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Inbox\u003C\u002Fstrong> is open mail that no task has labelled yet.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>A tab per label\u003C\u002Fstrong> is open mail carrying that label. Labels are whatever the member's tasks give a message; the\nOS has no fixed list, and a label with no open mail has no tab.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Archive\u003C\u002Fstrong> is everything closed that arrived, whatever its label: mail that was answered, and mail a task left\non purpose.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Sent\u003C\u002Fstrong> is everything the member sent: its tasks' replies and new mail, and the owner's.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Contacts\u003C\u002Fstrong> and \u003Cstrong>Signature\u003C\u002Fstrong>, for the owner, are on \u003Ca href=\"\u002Fdocs\u002Femail\u002Fwriting-mail\">Writing mail\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"handled-snoozed-and-archived\">Handled, snoozed and archived\u003C\u002Fh2>\n\u003Cp>Each message has a handled state. It is open while it is unhandled, waiting on a decision, or snoozed until a date\nand 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\nmessage, so it moves to Archive instead of staying under its label. A task records what it decided with\n\u003Ccode>os.mail_set_label\u003C\u002Fcode> and \u003Ccode>os.mail_set_handled\u003C\u002Fcode>, or about many messages at once with \u003Ccode>os.mail_set_many\u003C\u002Fcode>\n(\u003Ca href=\"\u002Fdocs\u002Femail\u002Fmail-in-tasks\">Mail in tasks\u003C\u002Fa>).\u003C\u002Fp>\n\u003Ch2 id=\"spam\">Spam\u003C\u002Fh2>\n\u003Cp>Mail that reaches Zero Human through its own receiving servers, as an attached domain's mail does, is scored for spam\non the way in. A message scored as spam is marked \u003Cstrong>Spam\u003C\u002Fstrong> in the list and when open, with its score, and a task\nreads the same score and flag on the message. A message scored far beyond that is refused at the door and never\nstored. Mail that was not scored shows no mark. See \u003Ca href=\"\u002Fdocs\u002Femail\u002Fsafety-and-deliverability\">Safety and deliverability\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"inbound-mail-a-day\">Inbound mail a day\u003C\u002Fh2>\n\u003Cp>Your plan caps how much inbound mail one mailbox takes in a day: 20 messages on Free and 100 on Starter. Company,\nScale and Enterprise have no daily cap. The day is the UTC day, so the count starts again at midnight UTC. Only mail\nstored in that mailbox counts, not another mailbox's and not its own sent copies, and a message delivered twice is\ncounted once.\u003C\u002Fp>\n\u003Cp>Mail past the cap that day is held, not lost. The OS keeps each such message as a hold, apart from the mailbox, so\nneither the member nor its tasks see it yet, and it counts towards your storage. The OS releases held mail by itself, oldest first: into\neach 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.\n\u003Cstrong>Billing\u003C\u002Fstrong> shows the mail taken today against the cap, and how many messages are held. A held message still not\nreleased when your plan's mail retention has passed is deleted, as stored mail is.\u003C\u002Fp>\n\u003Ch2 id=\"mailbox-buttons-and-their-schedules\">Mailbox buttons and their schedules\u003C\u002Fh2>\n\u003Cp>A task that declares a mailbox button (\u003Ccode>mailboxAction\u003C\u002Fcode>, \u003Ca href=\"\u002Fdocs\u002Fapi\u002Ftasks\">Tasks over the API\u003C\u002Fa>) and runs as a role the\nmember holds is offered above the member's list, or on each open mail, as a one-click button that starts it: the run\nreads this mailbox as the member's tasks always do, with the open mail's id for a button on one mail. A button over\nthe whole mailbox can also run on a schedule: the task's own schedule (\u003Ca href=\"\u002Fdocs\u002Fwork\u002Fschedules\">Schedules and webhooks\u003C\u002Fa>)\nstarts it as a run of the member, over the member's mailbox, exactly as pressing it would. \u003Ccode>GET \u002Fv1\u002Fmembers\u002F{id}\u002Fmailbox-actions\u003C\u002Fcode>, and \u003Ccode>os.member_mailbox_actions\u003C\u002Fcode> over the\n\u003Ca href=\"\u002Fdocs\u002Fmcp\">MCP server\u003C\u002Fa>, list the buttons; a task is started with \u003Ccode>POST \u002Fv1\u002Ftasks\u002F{id}\u002Fruns\u003C\u002Fcode> or \u003Ccode>os.start_task\u003C\u002Fcode>.\u003C\u002Fp>\n\u003Ch2 id=\"working-the-mailbox-by-hand\">Working the mailbox by hand\u003C\u002Fh2>\n\u003Cp>The enterprise owner can work a member's mailbox as a mail client: \u003Cstrong>Reply\u003C\u002Fstrong>, \u003Cstrong>Reply all\u003C\u002Fstrong>, \u003Cstrong>Forward\u003C\u002Fstrong>,\n\u003Cstrong>Archive\u003C\u002Fstrong> or \u003Cstrong>Move to inbox\u003C\u002Fstrong>, \u003Cstrong>Labels\u003C\u002Fstrong>, \u003Cstrong>Snooze\u003C\u002Fstrong> and \u003Cstrong>Delete\u003C\u002Fstrong> on a message, and \u003Cstrong>New mail\u003C\u002Fstrong> above the\nlist. \u003Cstrong>Move\u003C\u002Fstrong> hands a mail and the rest of its conversation to another mailbox in the company, another member's or\na person's, your own \u003Cstrong>Inbox\u003C\u002Fstrong> included, so you can answer it as yourself. How a mail is written is on\n\u003Ca href=\"\u002Fdocs\u002Femail\u002Fwriting-mail\">Writing mail\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>Anybody else reads the mailbox only, whatever their grant, and an API token or a connected app cannot act on it.\u003C\u002Fp>\n\u003Ch2 id=\"how-sending-from-a-member-is-approved\">How sending from a member is approved\u003C\u002Fh2>\n\u003Cp>A member's tasks send with \u003Ccode>os.mail_reply\u003C\u002Fcode> and \u003Ccode>os.mail_send\u003C\u002Fcode>, and every send waits for approval on the exact message\nfirst: the approval card shows the mail as it will leave, signature and quoted text included, and approving it sends\nthat and nothing more. A rejected or expired approval sends nothing. A reply goes out from the address the message it\nanswers arrived at, and threads under it, so the person reading it sees one conversation; the sent copy is filed in\nthe mailbox and listed under Sent. A run can only ever send from an address that delivers to its own member's mailbox.\u003C\u002Fp>\n\u003Cp>What the owner sends from the mailbox by hand leaves at once, as the member: the owner is who approves a member's\nsends, so nothing waits for one. See \u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fgates\">Gates and tool scopes\u003C\u002Fa> for how approvals work.\u003C\u002Fp>\n",[12,16,19,22,25,28,31,34],{"id":13,"text":14,"level":15,"planned":8},"the-inbox","The inbox",2,{"id":17,"text":18,"level":15,"planned":8},"tabs-and-labels","Tabs and labels",{"id":20,"text":21,"level":15,"planned":8},"handled-snoozed-and-archived","Handled, snoozed and archived",{"id":23,"text":24,"level":15,"planned":8},"spam","Spam",{"id":26,"text":27,"level":15,"planned":8},"inbound-mail-a-day","Inbound mail a day",{"id":29,"text":30,"level":15,"planned":8},"mailbox-buttons-and-their-schedules","Mailbox buttons and their schedules",{"id":32,"text":33,"level":15,"planned":8},"working-the-mailbox-by-hand","Working the mailbox by hand",{"id":35,"text":36,"level":15,"planned":8},"how-sending-from-a-member-is-approved","How sending from a member is approved",1794928143040]