[{"data":1,"prerenderedAt":32},["ShallowReactive",2],{"$fqpb4zhjq5f9b":3},{"href":4,"title":5,"description":6,"kind":7,"mark":7,"planned":8,"contributors":9,"provenance":7,"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, and whoever holds that role on\nthe task's team and is free does the next run. A role with no team is enterprise-wide: whoever holds it can take its\ntasks on any team that has no role of its own by that name.\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.\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 on the task's team and is free, the one who has waited longest first.\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 on the task's team holds the role, the task cannot start. The \u003Cstrong>Map\u003C\u002Fstrong> lists it under \u003Cstrong>Outside the team\nstructure\u003C\u002Fstrong>, with the reason.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2 id=\"a-role-and-its-team\">A role and its team\u003C\u002Fh2>\n\u003Cp>A role belongs to one team, or to none yet. That matters for the tasks on it: a run goes only to a holder of the role\non the task's team.\u003C\u002Fp>\n\u003Cp>A role created in the portal starts on no team. It joins one when a member who holds it becomes that team's\n\u003Ca href=\"\u002Fdocs\u002Fcompany\u002Fteams\">lead\u003C\u002Fa>: making a member lead moves their team-less roles to the team, along with the tasks they\ndo in them. Over the \u003Ca href=\"\u002Fdocs\u002Fapi\">API\u003C\u002Fa>, a role can be created on a team directly.\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, and replaces the same tool bound\non the member, 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-its-team","A role and its team",{"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,1791124519560]