> 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/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/set-campaign-boundaries.md).

# Set Campaign Boundaries

## Overview

The **Set Campaign Boundary** screen allows administrators to define the geographic and administrative areas where the campaign will be implemented.

Boundaries must be selected in **hierarchical order**, starting from the highest administrative level. Selecting a higher-level boundary enables the relevant lower-level options.

## Steps

### Step 1: Select the Highest Administrative Level

* Start by selecting the **Country** from the dropdown.

Once the country is selected, the next administrative level becomes available.

### Step 2: Select Lower Administrative Levels

Proceed level by level:

* Select the required **Province(s)** from the Province dropdown.
* Select the required **District(s)** from the District dropdown.
* Select the required **Administrative Post(s)** from the Administrative Post dropdown.

> Always follow the hierarchy from top to bottom to ensure valid selections.

### Step 3: Manage Selected Boundaries

For each boundary level:

* Use the dropdown to select one or more values.
* Selected boundaries will appear below the dropdown.
* Click the **Remove (✕)** icon to delete an individual boundary.
* Click **Clear All** to remove all selected boundaries at that level.

### Step 4: Verify Mandatory Selections

* Ensure that all mandatory boundary levels marked with an asterisk (\*) are selected before proceeding.

### Step 5: Continue to the Next Step

* Click **Next** to proceed to the next configuration step.
* To return to the previous screen without saving, use the **Back** option.

Your campaign boundaries are now configured.

<figure><img src="/files/7KT97kMfaB3UfYddt7iG" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.digit.org/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/set-campaign-boundaries.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.