Org structure
Draw your company: a circle with the organization's name on top, a tree of positions (defined by the structure — "café manager") and functions (appointed — "hygiene officer") below it. A member is appointed to every node and a deputy of that specific position is chosen. One person may hold several positions — with a different stand-in for each.
The deputies table — everything without drawing
An administrator finds the "Org structure and deputies" section in Organization settings. One button creates the structure, and the table handles the rest: add a position (including a subordinate one, with the plus in a row), rename right in the row, appoint holders and deputies, remove a position (the bin). Rows are indented by hierarchy and changes save immediately — a ✓ blinks after each save:
The structure map — the same source, just drawn
The table and the map are one source of truth: whatever you change in the table shows in the map, and vice versa. Administrators draw the map (the tree, moves, position/function kind in the node dialog); every member can read it — the user menu has an "Org structure" item:
The structure is not a project — it doesn't appear among the projects on the home page or in the tasks table, and tasks or deadlines cannot be attached to it. It describes who is who; the work lives in regular maps.
What it is for: rules aim at roles
Automation rules can target the position holder, the position deputy or the deputy of the responsible person — resolved at run time, so swapping people on positions breaks nothing. Typically: "deadline overdue → hand over to the deputy" or "the step started → assign the position holder". Details on the Deputies and dynamic targets page.
When a member leaves
When a member is removed, their positions are vacated automatically (holder and deputy) and administrators get a message to appoint replacements — nothing is left hanging on a non-existent address.