Locations: building the tree, managers and notification routing

Locations is your company laid out as a tree, up to four levels: Corporate, Project/Division, Location (a site, plant or building) and Area (a zone inside a site). Skip any level you don't need. Workers, assets, incidents and forms all point at a location.

Who can use it

Locations → Edit builds the tree. Changing notification routing needs the Manage notification routing right.

Build the tree

1. Admin side → Locations. + Add Corporate if there's no top level yet.
2. Click a node to edit it. + Add a location under it adds the next level down: name it and pick its type.
3. To move one, change Seated under on its Details tab.

A location's tabs

• Details: name, type and what it's seated under.
• Managers: this location's managers, and the managers it inherits from above. A location's manager hears about PINs filed there.
• Weather: its point on the map, the circle a phone uses to pick the site, and units. A location with no point uses the nearest one above it.
• Documents: files kept against the location.

How far up incident notices go

1. Locations → Notification Routing.
2. For each classification, pick how far up a PIN's notice goes: This location only, + Parent, + Parent and Corporate, or Full chain to Corporate.
3. Corporate standing recipients: people always told about incidents that reach Corporate.
4. One location different? Its Notify up to setting overrides the company default for every incident there.

These are live: the next incident filed at that classification follows them.

Removing a location

Remove this location shows what's still attached. Locations under it, and workers and assets set to it, must be moved first. A location with incidents or forms on file can't be deleted, only archived: it leaves active use and its records stay. Unarchive brings it back from the Archived tab.