QEHSadmin guide
Location hierarchy
Model your operational footprint — Organisation → Region → Site → Building → Floor → Zone — and scope records against it.
9 min read · 3 sections
Why locations?
Most QEHS records belong to a place. An inspection is "at the Dubai refinery". A permit is "at building B3, floor 2". Modelling your hierarchy lets you scope reports, dashboards, and permissions without rebuilding them per site.
Building the tree
- Open /settings/locations. Default tree: Organisation → Region → Site.
- Drag-and-drop to reorder. Indent to nest.
- Each node has: name, code (short identifier), address, coordinates, operating hours, timezone.
- Inactive sites hide from pickers but keep their history.
Location fields in modules
A Composer location field renders a tree-picker on the form. The selected node, and all its descendants via the "descendant match" option, drive scoped queries in dashboards and reports.