> 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-user-manual.md).

# HCM User Manual

A step-by-step guide to using the HCM mobile app for campaign operations and support functions

The HCM User Manual explains how to use the Health Campaign Management app in day-to-day field operations. It covers core support functions such as login, sync, help, navigation, and project selection.\
It also includes step-by-step guidance for campaign workflows, common actions, and feature-specific tasks. This section helps field teams, supervisors, and program staff use the app correctly during campaign delivery.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Support Functions</strong></td><td><a href="/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-user-manual/support-functions.md">Support Functions</a></td></tr><tr><td><strong>Campaign Types</strong></td><td><a href="/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-user-manual/campaign-types.md">Campaign Types</a></td></tr><tr><td><strong>Common Functions</strong></td><td><a href="/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-user-manual/common-functions.md">Common Functions</a></td></tr></tbody></table>


---

# 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/health/access/public-health-product-suite/health-campaign-management-hcm/hcm-user-manual.md?ask=<question>&goal=<user_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.