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

# HCM Console

## Overview <a href="#about-hcm-console" id="about-hcm-console"></a>

The **HCM Console** is a new tool within the Health Campaign Management (HCM) ecosystem that enables users to create and manage campaigns with ease. It’s designed for field-level health campaign managers who understand campaign structures but may not have technical expertise. The tool provides core campaign setup capabilities, with future releases planned for advanced customisation and automation.

## **Problems Addressed**

* **High developer dependency** – Campaign setup in the HCM app currently requires significant technical support.
* **Complex technical processes** – Users often need to understand JSON, APIs, or database schemas to make changes.
* **Time-consuming setup** – Configuring campaigns takes longer than necessary, slowing down implementation.
* **Limited user autonomy** – Field managers can’t easily make changes themselves during campaign planning or execution.

## **Goals & Benefits**

* **Empower non-technical users** – Provide an intuitive, guided interface for campaign setup and management.
* **Reduce setup time** – Allow quick creation of core campaign structures such as timelines, boundaries, targets, facilities, and users.
* **Enhance flexibility** – Enable real-time updates to campaigns during planning and execution.
* **Support gradual feature expansion** – Introduce advanced functions like form customisation and detailed data capture in future versions.
* **Increase efficiency and scalability** – Free up the technical team to focus on optimisation and expansion of the HCM platform.

## **Key Features** <a href="#key-features" id="key-features"></a>

* **Dual Timeline View** – Create and manage campaign timelines
* **Boundary Data Management** – Add or update boundaries
* **User Management** – Add/edit users for ongoing and upcoming campaigns
* **Target Management** – Add/edit targets for ongoing and upcoming campaigns
* **Facility Management** – Add/edit facilities for ongoing and upcoming campaigns
* **Campaign Enablement** – Set up ITN or similar health intervention campaigns directly from the console
* **Checklist Module** – Manage campaign checklists

With these tools, users can set up the **core structure** of their campaigns.

## User Role <a href="#user-role" id="user-role"></a>

<table><thead><tr><th width="140.48828125">User Role</th><th width="192.36328125">Scope of Action</th><th>Role Description</th></tr></thead><tbody><tr><td>System Admin</td><td>National Level/Provincial Level</td><td>The user will have all the data required for setting up a campaign and will be responsible for campaign setup on the DIGIT HCM app using the campaign data.</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 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/ph-v1.8/access/public-health-product-suite/health-campaign-management-hcm/hcm-console.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.
