The org chart

The Org chart view draws the company as a vertical tree: ownership at the top, management below it and, hanging from it, each role with its team. You open it from the left-hand menu, under «Org chart».

It is not decoration: the lines in the drawing are the real hierarchy. What hangs from a role here says who receives orders from whom, and whose desk the notices climb to when something happens.

The header

Element	What it shows
Title	«Who runs what».
Counter	«1 role» or «N roles». It counts the roles hanging from the tree, not counting ownership or management.

It counts both active and requested roles. That is the difference from the Team view, which only shows the active ones: here a role awaiting signature already appears in its place, with the «pending» mark, so you can see what the company will look like once you sign it.

How it is drawn

From top to bottom:

1. You, as ownership. It is the root node.
2. Management, hanging from you. That is the CEO: its node shows the job title «CEO» and the area «management».
3. The company’s branches, hanging from the CEO. Each branch is a role that depends directly on him; from each branch hang its own reports, and so on downwards with no limit on levels.
4. Your control team, in parallel with management. It sits in a separate group, with a shield and the label «Your control team», because it is not part of the chain of command: these are the roles that depend on you directly (an internal auditor, for instance). Each one unfolds its own tree if it has people reporting to it.

The lines joining the nodes are painted by the stylesheet: without them you could not tell who answers to whom.

What each node shows

Part	What it is
Name and job title	«Name · Job title». If the role has no proper name, only the job title.
Area	The role’s area; if empty, «no area». On the management node the job title «CEO» is shown. On the ownership node, «ownership».
«pending» mark	Only on roles with status «requested».

Roles can be clicked: doing so opens their record, the same one that opens from Team. Ownership and management are drawn as fixed nodes, with no record, because they are not hired roles. The CEO’s record opens from the Team view.

Cases the drawing puts in plain sight

Management has nobody. If the CEO has no role hanging from him, «Nobody reporting to him yet» appears below his node.

You have no control team. If no role depends on you, «Nobody watching yet. An internal auditor would hang from here, not from Adrián» appears below the group.

Roles with no place in the tree. If a role depends on a code that no longer exists (its manager was deleted, say), it does not vanish: it drops to a separate section at the end of the page, titled «No place in the tree», with this explanation: «They depend on someone who no longer exists. Open them and assign a manager». They open like any other and are fixed by changing their «Depends on».

How it is edited

This screen edits nothing. It is drawn from what is stored and has no buttons of its own. The hierarchy is changed in each role’s record, in the «Depends on» field of the Identity tab:

Option	What it means
Adrián (CEO)	The role joins the company’s chain of command and hangs from management.
You (control team)	The role moves to your branch, in parallel with management, and its scope changes to «control».
Another role	The role hangs from that other one, at whatever level it belongs.

The server checks two things before accepting the change:

• That the manager exists. If the code matches no role, the error says «there is no role código to depend on».
• That no circle is formed. If A manages B, B cannot manage A; the error says «that would make a circle: that role already depends on this one». Without this check, two roles would manage each other and neither would receive orders.

On saving, the org chart screen does not refresh itself: come back into the view (or reload) to see the new tree.

What the tree really decides

• Who gets notified. When you talk to a role directly, the notice climbs its chain of command. Those above read it on their next shift.
• Who delegates to whom. A role with the «Delegate» skill hands work out among those who depend on it, not among anyone.
• Who watches whom. Your control team hangs from you, not from the CEO. That separation is deliberate: blurring it would hide exactly what matters.