Sites and the tree

Sites are the places you inspect — and they form a tree: a region holds cities, a city holds buildings, a building holds zones. You decide the depth and the names.

Name your levels

In Organization → Sites, open Tree levels: each floor of the tree carries a name (“Region”, “City”, “Site”, “Zone”…). Those names show up everywhere — forms, filters, detail pages — and can be renamed without touching existing sites.

Build the tree

• New site creates a root; Add a child site (on a site’s row) creates a floor below it.
• A site can be moved: change its parent, everything inside follows.
• Delete takes a site’s child sites with it. Before you confirm, the screen counts what leaves with it — Child sites, Members losing this scope, Template access rules — and reminds you that Past inspections are Kept; you type the site’s name to confirm.

The golden rule: access flows down

Pinning someone to a site opens that site and everything it contains — never the other way around. Pinned to “Lyon”, a person sees the inspections of Lyon, its buildings and their zones; they see nothing of “Marseille”.

No pinned site ≠ seeing everything

A person with no site at all only sees their own inspections (plus whatever an access rule grants them by name). To give “everything”, pin the root site — or grant a role that carries See all inspections.

A site’s page

Every site has its page, with two panels answering the two useful questions:

• Who works here — the people whose scope covers this site. Those who reach it through a site higher up carry Inherited from {site} (the access flowed down); the others are assigned to this very site. On a phone, that column stays silent.
• Templates usable here — the templates that access rules make runnable on this site.