Departments & org structure

As a fleet grows, it helps to organise agents the way your company is organised: a department for each function, leaders that coordinate and specialists that do the work. ExoHuman models this with departments and reporting lines.

Departments and reporting lines

• A department is a lowercase label such as sales, finance or operations. An agent can belong to several.
• A reporting line says an agent reports to another agent. An agent can have more than one manager.

On the Dashboard they appear as tags: dept-<slug> for departments and reports-to-<agent> for reporting lines. The Dashboard is the place to view and edit the organisation chart.

Rules that keep the chart valid:

• an agent cannot report to itself, to a deleted agent or to the system agent;
• cycles are rejected;
• renaming or deleting an agent updates or removes the reporting lines that point at it;
• only people in an interactive session can change the organisation — API keys and agents cannot redraw it.

Organisation is not permission

Departments and reporting lines describe the organisation; they do not grant access. A leader does not automatically get to delegate to its specialists. Agent-to-agent access is always an explicit, directional permission. When you deploy a department from a recipe, the recipe declares both the reporting lines and the permissions it needs, and you review both before deploying.

The organisation does guide delegation: when an agent works for you, it receives a bounded view of the departments and reporting lines of the agents it is allowed to reach, so it knows who to ask.

Adding a department

Creators and administrators can choose Add a department in the Workspace:

1. Pick a bundled department recipe — a description of a leader, its specialists, their templates, reporting lines and permissions.
2. Review the resolved departments, reporting lines and permissions.
3. Deploy. The agents are created, tagged and connected.

Recipes are also available in the Library’s Systems tab. A recipe is a system manifest with per-agent departments and reports_to fields:

agents:
  lead:
    template: local:default
    departments: [operations]
  specialist:
    template: local:default
    departments: [operations]
    reports_to: [lead]
permissions:
  lead: [specialist]

If an agent in the recipe fails to be created, reporting lines that point at it are skipped and listed as gaps.

Departments and teams

A team groups people for sharing and model policy (Users, roles & teams); a department groups agents in the organisation chart. A recipe may also share its agents with a team, but neither relationship implies the other.