> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/complaints-management/access/configurator-onboarding-guide/setup-boundary.md). # Setup Boundary ## Overview Phase 2 defines the geographic hierarchy inside your tenant — the levels complaints get tagged to and routed through (e.g. State → District → City → Zone → Ward → Locality). Every complaint is ultimately tied to a Locality-level boundary. This hierarchy determines how complaints get aggregated and reported at every level above it.
**Before You Begin** * Phase 1 must be complete- Boundary Setup always applies to the tenant you created or selected there. * Decide which levels of hierarchy you actually need (at minimum 2, e.g. City → Ward). You can always add more boundary records later, but the level structure itself is harder to change once set. * Know in advance whether you want to pull your areas from OpenStreetMap (fast, less predictable) or define them yourself in Excel (slower, more reliable) — see the comparison below.
## Steps To start with the setup of boundary hierarchies, you have the following three options: * A boundary hierarchy already exists for this tenant. Click on **Proceed to Phase 3** to skip this step. * A boundary hierarchy already exists for this tenant. To add more boundaries: add them via **OpenStreetMap** or an **Excel upload.** * Boundary hierarchy does not exist? Create a new boundary hierarchy either with OpenStreetMap or upload as an Excel sheet. {% stepper %} {% step %} ### Fetch from OpenStreetMap
{% hint style="info" %} Note: The above image is illustrative only and does not reflect live or actual data. {% endhint %} Type your city or region name. The system queries OpenStreetMap and groups whatever it finds by administrative level. {% hint style="info" %} **Note:** Matching is done by name, and OSM sometimes stores areas under a local-language name that differs from what you'd naturally search for. Try an alternate spelling or the area's official/local name if your search comes up empty. {% endhint %} Now select levels. You'll see every administrative level OSM found, each with example place names. Select which levels to keep, and name each one (e.g. “Ward A”).
{% hint style="warning" %} **Warning:** You must select at least 2 levels, and your selection must be contiguous - you can't select City and Ward while skipping the level in between. {% endhint %} Review skipped areas. If some areas couldn't be matched, you'll see a list of what was skipped and why, before proceeding with the rest. {% hint style="warning" %} **Warning:** If a boundary hierarchy already exists on this tenant under the same name but with different level names than OSM is proposing, the system stops with an explicit error rather than risk mismatching your existing data. {% endhint %} Select **Create Boundaries**. Now, the loading screen creates your hierarchy and boundaries using the real map shapes pulled from OSM. Once successfully done, you will see a screen with the message **Phase 2 Complete!**.
Click on **Continue to Common** to move to Phase 3! {% endstep %} {% step %} ### Upload from Excel Click on **Upload from Excel.** You have the option to either create a new hierarchy or use an existing hierarchy.
**I. Use an existing hierarchy:** if a hierarchy structure already exists (e.g. inherited from the root tenant) and you just need to add boundary records to it. You'll pick from a list of existing hierarchies.
**II. Create a new hierarchy:** if this tenant has no boundary structure yet. Give it a name (e.g. ADMIN) and list its levels top-to-bottom (e.g. City, Ward, Locality) — minimum 2 levels.
Click on **Create Hierarchy** once the required fields are populated.
Download the boundary template, named Boundary\_Template\_{hierarchyType}.xlsx, and fill in one row per area. The template is in the following format: Assuming a Country → Ward two-level hierarchy
ColumnDescriptionExample
codeUnique code for the given areaCHESOEN
nameDisplay NameChesoen Ward
boundaryTypeWhich level this row belongs toWard
parentCodeThe code of the area directly above it in the hierarchyBomet
latitude/longitudeOptional coordinates
{% hint style="info" %} Note: The value assigned to the code column in this template is unique, whereas the display names can be similar across tenants. {% endhint %} Now upload the file in the **Drop your filled boundary template here** box.
Validate all the entries, resolve any errors if present and select the **Upload \ Boundaries** button.
Once successful, the screen shows you a **Boundaries Created Successfully!** message. You’ve completed Phase 2. Click the **Continue to Phase 3** button to proceed to the Common Masters step.
{% endstep %} {% endstepper %} --- # 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://docs.digit.org/complaints-management/access/configurator-onboarding-guide/setup-boundary.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.