> 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/campaign-management-dashboard/user-manual.md). # User Manual The DIGIT HCM provides a ready-to-use **Dashboard** that enables campaign supervisors to view real-time indicators, such as coverage, empowering them to make informed, data-driven decisions. ## Key Features * Download charts in PDF or JPG format. * Share charts via WhatsApp or email. * A diverse range of charts and graphs for visualising key metrics. * Drill-down functionality for detailed data examination. * Multi-language support. * Geographic boundary-based heat maps. * View data across multiple campaigns via a single dashboard. * Geo-coordinate map to view delivery data at the household level. * Restrict data access based on user hierarchy. * Tab navigation across modules. * Predictive charts to forecast campaign extensions and stock availability. * Custom Excel reports for in-depth analysis. * Filter and sort tables. * View data for custom date ranges or specific campaign cycles. ## User Roles The dashboard data is tailored according to the user's hierarchical boundary, ensuring access is aligned with their operational scope. For instance, a national supervisor can oversee campaign operations nationwide, while a district supervisor can solely access data within their designated district, without visibility into other districts. --- # 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/ph-v1.8/access/public-health-product-suite/campaign-management-dashboard/user-manual.md?ask=&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.