Skip to content

Teams and org chart

A team is a group of employees, and optionally members, that work toward a shared goal, such as Support or Month-end close. Teams give employees colleagues to hand work to, a shared memory, and a place in the org chart.

Field What it sets
Name Shown in the org chart and in hand-offs.
Goal One sentence on what the team delivers. Every employee in the team sees it.
Team owner The member accountable for the team. They’re the second step in the escalation chain.
Manager employee Optional. An employee that receives the team’s tasks, splits them and delegates the parts.
Employees The virtual employees in the team. Each employee belongs to one team.
Members Humans who work with the team. They can receive hand-offs and see the team’s activity.
Team knowledge Knowledge bases every employee in the team can search.
Team budget Optional. A cap on the combined spend of the team’s employees over a period.

Every workspace starts with a team called General. Create more teams under Teams > New team.

A manager employee is an employee whose job is to coordinate other employees. When a task arrives for the team, the manager employee:

  1. Reads the task and plans how to split it.
  2. Creates sub-tasks and assigns each one to the best-placed employee in the team, based on their skills, current load and track record.
  3. Follows the sub-tasks, answers questions from the team, and reassigns work when an employee is stuck.
  4. Combines the results and delivers the final answer.

A manager employee must be at L4 Delegate, because creating tasks for other employees is a Delegate action. It can’t give a team member more autonomy than that member has: each sub-task runs under the autonomy level, policies and budget of the employee who receives it.

A hand-off is when an employee passes a task, or part of it, to someone else. It’s recorded as a step in the run.

Hand-off to When it happens What the receiver gets
Another employee The task needs a skill the employee doesn’t have, such as a support agent passing a billing question to the finance employee. A new sub-task with the context, inputs and a link to the original run.
A human The employee can’t continue: missing information, a judgment call, or a customer who asks for a person. An item in their Orqane inbox and on their usual channel, with a summary and a suggested next step.
An outside agent The work belongs to an agent outside Orqane, reached over A2A. A request sent over A2A. Requires L4 Delegate.

Hand-offs to employees in another team are allowed if the receiving team accepts them. Set this on the team’s Settings tab, under Accept hand-offs from.

When a human takes a hand-off, they can answer and send the task back to the employee, or finish it themselves. Either way, the employee learns from the outcome through its memory.

Open Org chart in the sidebar to see the tree of teams, employees and human managers in your workspace.

  • Each card shows the employee’s name, role, status and autonomy level.
  • Lines show who manages whom: human managers, team owners and manager employees.
  • Click a card to open the profile. Click a team to see its goal, load and costs this month.
  • Use Filter to show only employees above an autonomy level, in a status, or with a wallet.

Drag an employee onto another team to move it. Orqane asks you to confirm the change of human manager if needed, and keeps the employee’s own memory. It loses access to the old team’s knowledge and gains the new team’s.

Each team has a team memory, separate from each employee’s own memory. Employees in the team write to it when they learn something useful to all, such as “Customer ACME prefers invoices in PDF”. Every employee in the team reads it at the start of a run.

  • Builders and the team owner can review, edit and delete entries on the team’s Memory tab.
  • An employee that leaves the team loses access to team memory, but keeps what it stored in its own memory.
  • Team memory follows the same access control and deletion rules as employee memory.