Organization structure
The organization structure (org chart) describes how your company is built: a tree of units (departments, teams, offices), each with a head, ordered deputies and members. For the rest of Kibo it serves one purpose only: knowing who decides a person's requests. It also gives automatic actions and forms recipients such as "the members of IT" or "the requester's manager".
Where
Organization → People → Org chart, for the owner and for anyone with permission to manage the org chart. Everyone can view it.
- Units: the tree; ⋯ on a unit adds a sub-unit, renames, moves, deletes.
- People: everyone with their units and who would decide their requests today; flags anyone without a unit or approver.
A person can belong to several units; one is their main unit, the one their requests go through.
Who decides a request
An example. Anna works in Sales, whose head is Marco. If Anna requests leave, Marco decides. If Marco is the one asking, the head of the unit above Sales decides. If Marco is missing or suspended, his first deputy decides; if there are none, the parent unit. Never the person who made the request. A vacation does not count as an absence: the request waits.
Deleting a unit
Sub-units and members move to the parent unit; the head and deputies lose their role; requests already sent do not change. There is no trash for the org chart. Deletion is refused as long as an automatic action, a form, a permission given to the unit or a job names it.
The assistant
It can look up units by name ("who heads IT?", "who is in Sales?") and use them in a draft automatic action. It never changes the org chart.
Plan
The org chart requires a plan that includes it. Without one, it becomes read-only and requests no longer reach the manager.