> 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/v2.1/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration/supervisor-workflows.md).

# Supervisor Workflows

## Overview

The **Supervisor Flow** begins after the System Administrator completes the microplan setup, including:

* Defining campaign boundaries
* Configuring facilities
* Setting assumptions and formulas
* Assigning user roles

Once setup is complete, supervisors can begin managing and operationalising the microplan.

## Supervisor Roles & Responsibilities

<table><thead><tr><th width="130.0390625">Role Name</th><th width="270.6640625">Role Code</th><th>Description</th></tr></thead><tbody><tr><td>Population Data Approver</td><td><code>POPULATION_DATA_APPROVER</code></td><td>Responsible for validating the population data, ensuring its accuracy, including the ability to edit data, approve, or send data back for correction.</td></tr><tr><td>Root Population Data Approver</td><td><code>ROOT_POPULATION_DATA_APPROVER</code></td><td>Responsible for validating the population data, ensuring its accuracy, including the ability to edit data, approve, or send data back for correction. Has additional permissions, including the ability to finalized population data.</td></tr><tr><td>Facility Catchment Mapper</td><td><code>FACILTIY_CATCHMENT_MAPPER</code></td><td>Responsible for assigning facility to villages.</td></tr><tr><td>Root Facility Catchment Mapper</td><td><code>ROOT_FACILITY_CATCHMENT_MAPPER</code></td><td>Responsible for assigning facility to villages. Has additional permissions, including the ability to finalized facility catchment.</td></tr><tr><td>Plan Estimation Approver</td><td><code>PLAN_ESTIMATION_APPROVER</code></td><td>Responsible for validating the plan data, ensuring its accuracy, including the ability to approve, or send data back for correction.</td></tr><tr><td>Root Plan Estimation Approver</td><td><code>ROOT_PLAN_ESTIMATION_APPROVER</code></td><td>Responsible for validating the plan data, ensuring its accuracy, including the ability to approve, or send data back for correction. Has additional permissions, including the ability to finalized estimation for microplan.</td></tr></tbody></table>

## UI Design

Browse through the linked pages to fetch UI configuration details for each screen.


---

# 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/v2.1/deploy/configuration/microplan-service-configuration/microplan-web-service-configuration/supervisor-workflows.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.
