> 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/configure-modules.md).
# Configure Modules
## Overview
The **Mobile App Configuration** screen allows administrators to set up and customise the functional modules available to field workers during campaign execution.
From this screen, you can:
* Control how beneficiaries are registered
* Define how services are delivered
* Manage referrals
* Track inventory
* Enable issue reporting
* Customise screen text and data fields
Each module can be configured independently. Changes made here directly affect the behaviour, workflow, and data capture experience in the mobile application.
## Steps
### Step 1: Open Module Configuration
1. On the Campaign Home Page, you will see a list of available mobile app modules.
2. Click **Configure** on the module you want to customise.
3. You will be redirected to the module-specific configuration screen.
### Step 2: Customise Screen-Level Content
Within the selected module:
1. Update **page headings** to reflect the campaign context.
2. Modify **descriptions** to provide clear instructions to field workers.
3. Review template elements displayed on the screen.
Customising this content ensures clarity and consistency for field users.
### Step 3: Manage Screen Fields
For each screen within the module, you can:
* **Add new fields** to capture additional data.
* **Remove existing fields** that are not required.
* **Update field labels** to improve clarity.
* **Edit helper text** to guide field workers on data entry.
* **Restrict Screenshots** disables screenshots on this screen in the mobile app to protect sensitive information.
Make sure all required data fields align with the campaign’s reporting and operational needs.
### Step 4: Save Changes
1. Review your configurations.
2. Click **Save Configuration** before exiting the module configuration screen.
Repeat the process for all required modules.
Your mobile app modules are now configured for campaign execution.
---
# 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/access/public-health-product-suite/health-campaign-management-hcm/hcm-console/configure-modules.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.
