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

# Custom Reports

## Overview

The Campaign Reports module gives campaign teams a single, consistent way to generate, monitor, and retrieve reports for a campaign. Instead of exporting data manually, a Campaign Manager selects the reports needed for a campaign once, and those reports are then generated automatically and made available to everyone with access to that campaign.

This manual is intended for two audiences:

* Campaign Managers who set up campaigns and need to configure which reports are generated and how often.
* Program Managers and National Supervisors who need to find, view, and download reports for the campaigns assigned to them.

It walks through the end-to-end flow: configuring reports during campaign setup, logging in to the dashboard, locating a campaign, and downloading a generated report.

## Key Features

#### Configurable report selection

Campaign Managers can choose exactly which reports apply to a campaign — Stock, Attendance, Beneficiary Visit List, Anomaly, Registered, and Adverse Reaction reports — instead of receiving a fixed, one-size-fits-all set.

#### Flexible, multi-select frequency

Each report can be scheduled independently, and more than one frequency (e.g. Daily and End of Campaign) can be applied to the same report.

#### Custom range reports

In addition to scheduled reports, users can generate a report for a specific custom date range on demand, without waiting for the next scheduled run.

#### Campaign-scoped dashboard access

Program Managers and National Supervisors see only the campaigns assigned to them, with reports automatically scoped to each campaign — no separate configuration is needed on their end.

#### Real-time generation status

Each report shows a live status (In Progress or Completed) with a progress indicator, so users know when a report is ready.

#### One-click download

Completed reports can be downloaded directly from the report detail screen, along with their triggered time and file size.

#### PII awareness

Reports containing personally identifiable information are clearly labelled as **Contains PII**, prompting users to handle downloaded files in line with data protection policy.

## User Roles

<table><thead><tr><th width="182.66015625">Role</th><th width="292.31640625">What they do</th><th>Where</th></tr></thead><tbody><tr><td>Campaign Manager</td><td>Selects report types and sets their frequency during campaign setup.</td><td>Campaign home page → Configure Reports</td></tr><tr><td>Program Manager / National Supervisor</td><td>Views assigned campaigns, opens campaign-scoped reports, and downloads completed reports.</td><td>Dashboard → My campaigns → View Reports</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/access/public-health-product-suite/health-campaign-management-hcm/custom-reports.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.