[{"data":1,"prerenderedAt":32},["ShallowReactive",2],{"$f3a1zow4zx4mbu":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\u002Froles","Roles","A role is a job: the tasks done in it, the members who hold it, and the tools and caps that come with it.",null,false,[],"\u003Ch2 id=\"what-a-role-is\">What a role is\u003C\u002Fh2>\n\u003Cp>A role is a job, such as Onsite SEO or Product Engineer. It is defined by the tasks done in it, and held by\nmembers. A member can hold several roles, and a role can be held by several members.\u003C\u002Fp>\n\u003Cp>Roles are how work finds a member. A task is given to a role, never to one person or one team, and whoever holds\nthat role and is free does the next run, on whatever team they sit. A role belongs to no team: it is one job across\nthe company, and the same role is held on every team one of its holders sits on. A team's tasks are the tasks of the\nroles its members hold. Two project teams can each have a CTO by seating a different holder of the CTO role on each:\nboth teams then have the CTO's tasks, and each run goes to whichever holder is free.\u003C\u002Fp>\n\u003Ch2 id=\"creating-a-role\">Creating a role\u003C\u002Fh2>\n\u003Cp>\u003Cstrong>Roles → 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>Name\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>The job's name.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Slug\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Its short name, taken from the name if you leave it blank. Unique in the enterprise.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>\u003Cstrong>Members\u003C\u002Fstrong>\u003C\u002Ftd>\n\u003Ctd>Who holds it. You can add holders later.\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\n\u003C\u002Ftable>\n\u003C\u002Fdiv>\n\u003Cp>You can also give a member a role from their own page, or when you create them and put them on a team. Seat them on\nthe team they work for: their runs use that team's tools, caps and memory, and the role's tasks become that team's\ntasks too.\u003C\u002Fp>\n\u003Ch2 id=\"tasks-on-a-role\">Tasks on a role\u003C\u002Fh2>\n\u003Cp>On a role's page, \u003Cstrong>Manage tasks\u003C\u002Fstrong> adds a task to the role or takes it off. The page then draws the role's tasks as a\nworkflow, with the handoffs in and out of each.\u003C\u002Fp>\n\u003Cp>A task on a role runs for its holders:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Each run goes to a member who holds the role and is free, on any team or on no team, the one who has waited\nlongest first. A holder whose teams are all switched off is skipped; a holder on no team can still take it.\u003C\u002Fli>\n\u003Cli>Ready holders come first. A holder is ready for a task when a tool binding of theirs (their own, their role's,\ntheir team's or the company's) reaches every tool the task needs, and a model credential is connected for them.\nThe run goes to a ready holder, the one longest idle first among them, even if another holder has never run. A\nnew member is not handed work their tools cannot do. A task that runs no model (\u003Ccode>deterministic\u003C\u002Fcode>) has no tools and\nneeds no credential, so every holder is ready for it.\u003C\u002Fli>\n\u003Cli>If a ready holder is busy, the run waits for them (\u003Ccode>member_busy\u003C\u002Fcode>) rather than go to a holder who cannot run it.\u003C\u002Fli>\n\u003Cli>If no holder is ready, the run goes to the holder it always would have, longest idle first. It then stops before it\nstarts. A tool nobody bound stops it with \u003Ccode>tool_not_bound\u003C\u002Fcode> naming the tools, and the company owner gets a\nmissing-binding notice in \u003Cstrong>Needs you\u003C\u002Fstrong> naming the member and the tools; binding them resumes the run. A holder\nwith no model credential connected stops it with \u003Ccode>llm_not_bound\u003C\u002Fcode> instead, which the notice does not cover.\u003C\u002Fli>\n\u003Cli>If every holder is busy, work that arrived by handoff, retry, webhook or chat waits for the first to be free.\u003C\u002Fli>\n\u003Cli>If nobody holds the role, the task cannot start. The \u003Cstrong>Map\u003C\u002Fstrong> lists it under \u003Cstrong>Outside the team structure\u003C\u002Fstrong>, with\nthe reason.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"a-role-and-the-teams-it-is-held-on\">A role and the teams it is held on\u003C\u002Fh2>\n\u003Cp>A role belongs to no team. It is held on every team one of its holders sits on, and the role's page lists those teams\nunder \u003Cstrong>Held on\u003C\u002Fstrong>. Each of those teams has the role's tasks. A run is done for the teams of the member it goes to:\nput a member on a team and their runs use that team's tools, caps and memory.\u003C\u002Fp>\n\u003Cp>There is one copy of each task, whichever teams have it. Cloning a role from the \u003Ca href=\"\u002Fdocs\u002Fcommunity\u002Froles\">Catalog\u003C\u002Fa>\nonto a second team reuses the role and the tasks you already have, and installs only the tasks you lack, under their\nown names. The team you pick is where the role's holder is seated.\u003C\u002Fp>\n\u003Ch2 id=\"what-comes-with-a-role\">What comes with a role\u003C\u002Fh2>\n\u003Cp>A role is also a layer that tools and caps attach to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>\u003Cstrong>Tools.\u003C\u002Fstrong> A tool bound to a role reaches the work of every member who holds it, on every team they hold it on,\nand replaces the same tool bound on their team or the enterprise (\u003Ca href=\"\u002Fdocs\u002Ftools\">tool directory\u003C\u002Fa>).\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Spend.\u003C\u002Fstrong> A cap set on a role applies to the runs of every member who holds it, alongside every other cap that\napplies (\u003Ca href=\"\u002Fdocs\u002Fcontrol\u002Fspend\">Spend and models\u003C\u002Fa>).\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cdiv class=\"prose__planned\">\n\u003Cp class=\"prose__flag\">Planned\u003C\u002Fp>\n\u003Ch2 id=\"coming-for-roles\">Coming for roles\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>Changing and deleting a role.\u003C\u002Fstrong> Renaming a role, and deleting one nobody needs any more. Today a role's\nholders and tasks can change, but the role itself cannot be renamed or deleted.\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Public roles to clone.\u003C\u002Fstrong> A role with all its tasks, cloned from another company and ready to give to one of\nyour members. See the \u003Ca href=\"\u002Fdocs\u002Fcommunity\u002Froles\">role directory\u003C\u002Fa>.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fdiv>\n",[12,16,19,22,25,28],{"id":13,"text":14,"level":15,"planned":8},"what-a-role-is","What a role is",2,{"id":17,"text":18,"level":15,"planned":8},"creating-a-role","Creating a role",{"id":20,"text":21,"level":15,"planned":8},"tasks-on-a-role","Tasks on a role",{"id":23,"text":24,"level":15,"planned":8},"a-role-and-the-teams-it-is-held-on","A role and the teams it is held on",{"id":26,"text":27,"level":15,"planned":8},"what-comes-with-a-role","What comes with a role",{"id":29,"text":30,"level":15,"planned":31},"coming-for-roles","Coming for roles",true,1794928142814]