> For the complete documentation index, see [llms.txt](https://documentation.opencrvs.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.opencrvs.org/v2.0/technical/guides/configuration/administrative-hierarchy/locations.md).
# Locations
Unlike administrative areas, a location refers to a more specific point. Usually, a location is a physical place such as an office, health facility, or police station.
Locations serve two purposes:
* A precise, identifiable place where an event occurs (e.g. a mother gave birth at Ezhi District Hospital).
* A place of assignment for staff (e.g. Kunda Simbaya, Registration Agent, works at Irundu District Office).
Locations are configured within the administrative hierarchy. Learn how locations affect [roles, scopes and jurisidictions](https://app.gitbook.com/o/zub8C4BetmW3a9Bj4Cd4/s/TIJguU5Pzi7HeHrkXa4I/~/edit/~/changes/126/technical/guides/configuration/users/roles-and-scopes)
Example 1: Simple, populated administrative hierarchy
Locations sit within administrative areas.
* An administrative area may have zero or more locations.
* A location may have zero or more users.
Example 2: Locations directly under country
Locations can be placed directly under a country, without belonging to any administrative area.
Unless restricted, users assigned to locations directly under a country have jurisdiction over the entire country.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.opencrvs.org/v2.0/technical/guides/configuration/administrative-hierarchy/locations.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
