---
sourceDocument: Australia Employee Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/employee-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Location hierarchy and child locations

# Location hierarchy and child locations {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

The list of impacted people is populated based on the selected location and includes individuals from any child locations in the Location \[cmn_location\] table hierarchy.

The Location table supports a hierarchical parent-child structure, so child locations are nested under primary parent locations. Each child location can also have its own child
locations.

When a critical event is assigned to a parent location, the system automatically includes all individuals associated with that location and any child locations. For example, selecting USA as the parent location (Location1) would
include child locations such as California (Location2).

To configure, see [Define a location hierarchy](https://www.servicenow.com/docs/access?context=define-tni-locations&version=australia&pubname=australia-telecom-network-inventory&ft:locale=en-US)