The Two-Level Hierarchy
OpenStudio uses a strict two-level hierarchy to organize users and permissions. Understanding this structure is essential before creating or editing structures, assigning users, or configuring HR and access control rules.
Level 1 — Areas (Macro-Structures)
An Area is the highest grouping unit (e.g., Human Resources, General Direction, Financial Area).
- Manager: Each Area is led by an Area Manager who appears on the org chart and in reporting views.
- Role: Areas act as containers for Departments. Users are never assigned directly to an Area.
- Code: A unique alphanumeric code assigned at creation — permanent and cannot be changed afterwards.
- Deletion rule: An Area can only be deleted when it contains no active Departments.
Level 2 — Departments (Operational Units)
A Department is a specific operational unit nested inside an Area (e.g., Payroll Unit inside Human Resources).
- Head of Unit: Each Department has a designated Head of Unit responsible for that structure.
- Role: Users are physically assigned to a Department — this becomes their referral structure.
- Code (Unique ID): A unique alphanumeric code used for permission referencing and internal lookups.
- Parent Area: A Department always belongs to exactly one Area. It can be moved to a different Area by authorised administrators.
Key rule: Users are always assigned to a Department, never directly to an Area. The user count shown on an Area row in the list aggregates all users across every Department in that Area.
Who can manage structures?
| Permission | What it allows |
|---|---|
| Founder | Full access to all structure operations. |
gestione_dipartimenti | Create, edit, and view Areas and Departments. |
can_delete_structures | Delete Areas and Departments (moves them to the Recycle Bin). |
can_move_departments | Move a Department from one Area to another. |
can_recycle_structures | Access the Recycle Bin and restore deleted structures. |
