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.
What a role is
A role is a job, such as Onsite SEO or Product Engineer. It is defined by the tasks done in it, and held by members. A member can hold several roles, and a role can be held by several members.
Roles are how work finds a member. A task is given to a role, never to one person or one team, and whoever holds that role and is free does the next run, on whatever team they sit. A role belongs to no team: it is one job across the 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 roles its members hold. Two project teams can each have a CTO by seating a different holder of the CTO role on each: both teams then have the CTO's tasks, and each run goes to whichever holder is free.
Creating a role
Roles → Create, in the portal:
| Field | What it is |
|---|---|
| Name | The job's name. |
| Slug | Its short name, taken from the name if you leave it blank. Unique in the enterprise. |
| Members | Who holds it. You can add holders later. |
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 the team they work for: their runs use that team's tools, caps and memory, and the role's tasks become that team's tasks too.
Tasks on a role
On a role's page, Manage tasks adds a task to the role or takes it off. The page then draws the role's tasks as a workflow, with the handoffs in and out of each.
A task on a role runs for its holders:
- 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 longest first. A holder whose teams are all switched off is skipped; a holder on no team can still take it.
- Ready holders come first. A holder is ready for a task when a tool binding of theirs (their own, their role's,
their team's or the company's) reaches every tool the task needs, and a model credential is connected for them.
The run goes to a ready holder, the one longest idle first among them, even if another holder has never run. A
new member is not handed work their tools cannot do. A task that runs no model (
deterministic) has no tools and needs no credential, so every holder is ready for it. - If a ready holder is busy, the run waits for them (
member_busy) rather than go to a holder who cannot run it. - If no holder is ready, the run goes to the holder it always would have, longest idle first. It then stops before it
starts. A tool nobody bound stops it with
tool_not_boundnaming the tools, and the company owner gets a missing-binding notice in Needs you naming the member and the tools; binding them resumes the run. A holder with no model credential connected stops it withllm_not_boundinstead, which the notice does not cover. - If every holder is busy, work that arrived by handoff, retry, webhook or chat waits for the first to be free.
- If nobody holds the role, the task cannot start. The Map lists it under Outside the team structure, with the reason.
A role and the teams it is held on
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 under Held on. Each of those teams has the role's tasks. A run is done for the teams of the member it goes to: put a member on a team and their runs use that team's tools, caps and memory.
There is one copy of each task, whichever teams have it. Cloning a role from the Catalog onto a second team reuses the role and the tasks you already have, and installs only the tasks you lack, under their own names. The team you pick is where the role's holder is seated.
What comes with a role
A role is also a layer that tools and caps attach to:
- Tools. A tool bound to a role reaches the work of every member who holds it, on every team they hold it on, and replaces the same tool bound on their team or the enterprise (tool directory).
- Spend. A cap set on a role applies to the runs of every member who holds it, alongside every other cap that applies (Spend and models).
Planned
Coming for roles
- Changing and deleting a role. Renaming a role, and deleting one nobody needs any more. Today a role's holders and tasks can change, but the role itself cannot be renamed or deleted.
- Public roles to clone. A role with all its tasks, cloned from another company and ready to give to one of your members. See the role directory.