Skip to content

Org structure ​

What it is for: so that a rule can say “hand over to the shift lead” or “notify the deputy” and you never rewrite names in it when someone changes. 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.

Where to find it and how to start ​

An administrator and a structure manager have the Org structure and deputies section in Organization settings; the structure map opens from the Org structure item in the user menu (a member sees it only once the structure exists).

  1. Organization settings → Org structure and deputies → Create structure.
  2. Add position (or Add subordinate position with the plus in a row) and name it — say “café manager”. A new structure manager first gets an Organization notification about the appointment.
  3. Pick the Holder and the Deputy in the row. What you see: Saved ✓ blinks after every change.

The deputies table — everything without drawing ​

The table handles everything: 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 and structure managers draw the map (the tree, moves; the node window has a Position category instead of Assignment, with Position / function name, Kind, Holder and Deputy of this position; the card has an Add subordinate button and a vacant tag); 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 and structure managers get a message to appoint replacements — nothing is left hanging on a non-existent address.

The assistant can read and change the structure too (“who covers for the shift lead?”, “appoint Peter as the internal auditor”).

Limits

  • Deleting the structure is for an administrator only; a structure manager draws and staffs it.
  • The structure map cannot be shared through the Share dialog or archived; it has no project number.
  • Uploading an account export does not create the structure (the project is openly skipped).
  • A member without an existing structure does not see the menu item.

Open source under the MIT license · © Tengo s.r.o.