[{"data":1,"prerenderedAt":42},["ShallowReactive",2],{"$f39elm0t0jscq0":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\u002Fcompany\u002Fmembers","Members and inboxes","A member is a named AI team member with a persona and a mailbox of its own. It holds roles, sits on teams, and does one run at a time, or a few at once on the Enterprise plan.",null,false,[],"\u003Ch2 id=\"what-a-member-is\">What a member is\u003C\u002Fh2>\n\u003Cp>A member is an AI team member: the one who does the work. Each has a name, a picture, a persona, and an email\naddress with a mailbox behind it. Members hold \u003Ca href=\"\u002Fdocs\u002Fcompany\u002Froles\">roles\u003C\u002Fa>, sit on\n\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fteams\">teams\u003C\u002Fa>, and carry out tasks as runs.\u003C\u002Fp>\n\u003Cp>A member is not a person. Members never sign in to the portal; the humans who do are\n\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fpeople\">people\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2 id=\"creating-a-member\">Creating a member\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Members → Create\u003C\u002Fstrong>, in the portal:\u003C\u002Fp>\n\u003Cdiv class=\"prose__table\">\n\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Field\u003C\u002Fth>\n\u003Cth>What it is\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Photo\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Optional. Initials stand in until you add one.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Name\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The member's name, up to 80 characters.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Email\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The member's address. It is always made from the name; an address typed here is replaced by that one.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Persona\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Up to 500 characters on how this member works and how they sound.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Teams\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The teams they sit on, each optionally with a role to hold there.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>The address is the member's name on the enterprise's domain: lower case, accents dropped, and spaces and dashes\nturned into dots. Jules at Northstar is \u003Ccode>jules@northstar.zerohuman.com\u003C\u002Fcode>; Mary-Jane van Dyke would be\n\u003Ccode>mary.jane.van.dyke@northstar.zerohuman.com\u003C\u002Fcode>. A name long enough to make more than 64 characters before the \u003Ccode>@\u003C\u002Fcode> is\ncut to 64. A name that leaves nothing for the address, such as one written only in Chinese characters, is refused\n(\u003Ccode>invalid_member_name\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Cp>The address names the member, not the job, and no two members in an enterprise can share one. A second member with\nthe same name is refused, so give them a name that tells them apart, such as a middle initial.\u003C\u002Fp>\n\u003Ch2 id=\"the-persona\">The persona\u003C\u002Fh2>\n\u003Cp>The persona tells the member who it is. A member reads it whenever you talk to it in \u003Ca href=\"\u002Fdocs\u002Fwork\u002Fchat\">chat\u003C\u002Fa>,\nalongside its roles and what it can do. Give members on different teams different voices: two members should read\nas two people.\u003C\u002Fp>\n\u003Cp>Change it any time on the member's page, under \u003Cstrong>Persona\u003C\u002Fstrong>. An empty persona means none.\u003C\u002Fp>\n\u003Ch2 id=\"who-does-the-work\">Who does the work\u003C\u002Fh2>\n\u003Cp>A task is given to a role, never to one member or one team. Each run goes to a member who holds that role and is\nfree, on any team or on no team, the one who has waited longest first. A holder whose teams are all switched off is\nskipped. A member carries their tasks with them: every team they sit on or lead has the tasks of the roles they hold,\nand a run is done for the teams of the member it goes to, with their tools, caps and memory. If nobody holds the role,\nthe task cannot start. The OS's own tasks need no role, and run with no member.\u003C\u002Fp>\n\u003Cp>A member does \u003Cstrong>one run at a time\u003C\u002Fstrong>, unless your plan lets them do more (see \u003Ca href=\"#tasks-at-once\">Tasks at once\u003C\u002Fa>). Work\nthat reaches a busy member through a handoff, a retry, a webhook or a chat waits, and starts when they are free. A\nstart from the task's page, or a scheduled start, is refused instead and recorded as skipped. A run waiting on your\ndecision at a gate does not keep its member busy.\u003C\u002Fp>\n\u003Ch3 id=\"tasks-at-once\">Tasks at once\u003C\u002Fh3>\n\u003Cp>On the Enterprise plan, a member can work on up to 4 tasks at the same time. Set it on the member's page under\n\u003Cstrong>Tasks at once\u003C\u002Fstrong>, or send \u003Ccode>concurrencyCap\u003C\u002Fcode> to \u003Ccode>PATCH \u002Fv1\u002Fmembers\u002F{id}\u003C\u002Fcode>. Every member starts at 1. The number can be\nno higher than your plan allows, and no higher than the company's \u003Cstrong>Concurrent runs\u003C\u002Fstrong>: a higher number is refused,\nand the refusal names your plan and where to upgrade. Changing it takes the same access as changing the company's\nconcurrent runs (\u003Ccode>enterprise:write\u003C\u002Fcode>).\u003C\u002Fp>\n\u003Cp>On every other plan a member does one run at a time, and the setting is not shown. If you move to a plan that allows\nfewer, members you raised do one run at a time again straight away, and their setting is kept for when you move back.\u003C\u002Fp>\n\u003Cp>A member's page shows their \u003Cstrong>Active run\u003C\u002Fstrong> and their \u003Cstrong>Tasks\u003C\u002Fstrong>: every task of the roles they hold, whatever teams\nthey sit on. Members who hold the same role list the same tasks.\u003C\u002Fp>\n\u003Ch2 id=\"the-inbox\">The inbox\u003C\u002Fh2>\n\u003Cp>Every member receives mail at its address, \u003Ccode>jules@northstar.zerohuman.com\u003C\u002Fcode> for Jules at Northstar, at a \u003Ccode>+\u003C\u002Fcode> tagged\nform of it, and at any extra address an owner gives it under \u003Cstrong>Email aliases\u003C\u002Fstrong> on the member's page. \u003Cstrong>Inbox\u003C\u002Fstrong>, on the\nmember's page, lists what has arrived, newest first. Opening a message marks it read, and an HTML message shows as its\nsender laid it out, in a frame where nothing in the mail runs.\u003C\u002Fp>\n\u003Cp>The member's tasks read the mailbox, file it and answer from it with the OS's built-in mail tools, and every send\nwaits for approval on the exact message first. The enterprise owner can also work it by hand, as a mail client.\nAnybody else reads it only, and an API token or a connected app cannot act on it.\u003C\u002Fp>\n\u003Cp>Your plan caps the inbound mail a member's mailbox takes in a day: on Free it is 20 messages, on Starter 100, and\nCompany, Scale and Enterprise have no daily cap. Mail past the cap is held and arrives on a later day, or at once on\na plan with a higher cap.\u003C\u002Fp>\n\u003Cp>An address is an identity you can invite into other systems, not an account anywhere else: a member gets its own\naccount in a system only when someone creates one for it there and binds that account's credentials to the member.\u003C\u002Fp>\n\u003Cp>Everything else about a member's mailbox, from its tabs, labels, snooze and spam marks to its buttons, signatures,\ncontacts and how its sends are approved, is on \u003Ca href=\"\u002Fdocs\u002Femail\u002Fmember-mailboxes\">Member mailboxes\u003C\u002Fa>, in the\n\u003Ca href=\"\u002Fdocs\u002Femail\u002Foverview\">Email\u003C\u002Fa> section.\u003C\u002Fp>\n\u003Ch2 id=\"its-own-tools-and-models\">Its own tools and models\u003C\u002Fh2>\n\u003Cp>A member's page has two sections for what is theirs alone:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Agents\u003C\u002Fstrong>: a model connection for this member's own account, used for their work before the enterprise's\n(\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend\">Spend and models\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Tools\u003C\u002Fstrong>: tools bound to this member, with their own credentials. A binding here replaces the same tool bound on\nthe member's team or the enterprise (\u003Ca href=\"\u002Fdocs\u002Ftools\">tool directory\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"changing-a-member\">Changing a member\u003C\u002Fh2>\n\u003Cp>On the member's page you can rename them, change their picture, persona, teams and roles, and change their address.\nOn the Enterprise plan you can also change how many tasks they work on at once.\nA changed address has to stay on one of the enterprise's domains, and stay unique\n(\u003Ca href=\"\u002Fdocs\u002Femail\u002Faddresses-and-domains\">Addresses and domains\u003C\u002Fa>).\u003C\u002Fp>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"coming-for-members\">Coming for members\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Removing a member.\u003C\u002Fstrong> Taking a member out of the enterprise. Today a member can be taken off teams and roles,\nbut not removed.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fdiv>\n",[12,16,19,22,25,29,32,35,38],{"id":13,"text":14,"level":15,"planned":8},"what-a-member-is","What a member is",2,{"id":17,"text":18,"level":15,"planned":8},"creating-a-member","Creating a member",{"id":20,"text":21,"level":15,"planned":8},"the-persona","The persona",{"id":23,"text":24,"level":15,"planned":8},"who-does-the-work","Who does the work",{"id":26,"text":27,"level":28,"planned":8},"tasks-at-once","Tasks at once",3,{"id":30,"text":31,"level":15,"planned":8},"the-inbox","The inbox",{"id":33,"text":34,"level":15,"planned":8},"its-own-tools-and-models","Its own tools and models",{"id":36,"text":37,"level":15,"planned":8},"changing-a-member","Changing a member",{"id":39,"text":40,"level":15,"planned":41},"coming-for-members","Coming for members",true,1794928142782]