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

# Configuration

This section offers a comprehensive guide to setting up and tailoring the HCM platform for your deployment. It’s your go-to spot for all configuration needs and is organised into four key areas (refer and click on the cards below for details).

<table data-card-size="large" data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><mark style="color:blue;"><strong>Campaign &#x26; Country Specific Configuration</strong></mark></td><td>Establishes regional and campaign-level settings—think localisation preferences, campaign structures, and any adaptations unique to your environment.</td><td><a href="/health/deploy/configuration/campaign-and-country-specific-configuration.md">Campaign &amp; Country Specific Configuration</a></td></tr><tr><td><mark style="color:blue;"><strong>HCM Service Configuration</strong></mark></td><td>Covers backend service setups and defines how each component of HCM behaves and integrates.</td><td><a href="/health/deploy/configuration/hcm-service-configuration.md">HCM Service Configuration</a></td></tr><tr><td><mark style="color:blue;"><strong>HCM UI Configuration</strong></mark></td><td>Configure UI elements like login screens, language selectors, dashboards, stock management views, and attendance-related structures—customising how users interact with the system.</td><td><a href="/health/deploy/configuration/hcm-ui-configuration.md">HCM UI Configuration</a></td></tr><tr><td><mark style="color:blue;"><strong>HCM Dashboard Configurations</strong></mark></td><td>Guides the design and setup of operational dashboards—like IRS chart layouts, MDMS-driven configurations, integration with Kibana dash­boards, and how live data is displayed and visualised.</td><td><a href="/health/deploy/configuration/hcm-dashboard-configurations.md">HCM Dashboard Configurations</a></td></tr><tr><td><a href="/health/deploy/configuration/hcm-console-configuration.md"><mark style="color:blue;"><strong>HCM Console Configurations</strong></mark></a></td><td>Configure HCM Console, project factory, UI, campaign details and excel ingestion facilities</td><td></td></tr><tr><td><a href="/health/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration.md"><mark style="color:blue;"><strong>Microplan Service Configurations</strong></mark></a></td><td>Configure microplan services, UI and related features </td><td></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/deploy/configuration.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.