Feature · Organization
Roles
Define worker roles and their responsibilities.
How it works
Built-in roles
- Software Engineer: takes a ticket from intake to a merged change, with the smallest root-cause fix.
- QA Engineer: risk-based testing, reproductions and regression tests.
- DevOps Engineer: infrastructure as code, staged rollouts and incident response.
- Support Agent: solves customer issues and escalates what needs a person.
- Product Manager: turns problems into prioritised specs with acceptance criteria.
- Researcher: investigates primary sources and cites every claim.
- Analyst: answers business questions with data work that others can repeat.
- Technical Writer: writes documentation that is checked against the code and the product.
Roles for the chart
- Chief Executive: your front door and the top of the chart.
- Department Head: runs one department, delegates and reports up.
- Chief of Staff: sorts oversight findings into incidents and recommends what to do.
How roles inherit
Each role above extends Employee, which extends Worker. A role inherits the instructions and capabilities of the role it extends. The Roles page shows the layers.
Add a role
An owner or admin selects New role, or Extend on an existing role. A new role has an id, a name, the role it extends, instructions, responsibilities, capabilities and evaluation criteria. Ids cannot change. Select Hire into role to create a worker with it.
From the help article Roles, checked against the product on .
What you can do
The operations this feature's screens call. Each one is POST /api/<name>, and the badge says who may call it.
ViewerlistWorkersLists workers.
Types:
ListWorkersRequestreturnsListResponse<WorkerSummary>
AdminNo API tokensupsertRoleSaves the role.
Types:
UpsertRoleRequestreturnsRoleDto
ViewerlistRolesLists roles.
Types:
EmptyRequestreturnsListResponse<RoleDto>
Screens
/roles/roles/:id