> 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/login.md).

# Login

## Overview

This page explains how to log in to the HCM Console. Program teams use the Console to configure, manage, and run health campaigns.

**Who Can Log In**

* Campaign Managers
* ICT4D team members

## Steps

### Step 1: Open the Console

1. Open a web browser (Chrome, Firefox, Edge, etc.).
2. Enter the HCM Console URL provided by your implementation team.

#### Step 2: Enter Your Credentials

1. On the login screen, enter your **username** and **password**.
2. These credentials are shared with you by the implementation team.
3. Click **Login**.

<figure><img src="/files/236rrUsVp6icXwfpWmdP" alt=""><figcaption></figcaption></figure>

#### Step 3: Access Campaigns

Once logged in, you will land on the dashboard. From here, you can:

* Select **Create Campaign** to set up a new campaign, or
* Select **My Campaigns** to view and manage existing campaigns.

<figure><img src="/files/cNHGYUAlwJsz5IcaEjin" alt=""><figcaption></figcaption></figure>

You are now ready to start configuring and managing campaigns.


---

# 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/login.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.