> 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/specifications/role-action-mapping.md). # Role Action Mapping ## Overview This section defines which actions each system role is authorised to perform, ensuring clear, secure, and role-appropriate access within the Console and mobile application. Initial mappings are available for **System Administrator**, **Registrar**, and **Distributor**, with additional roles in progress. ## Mapping
RolesDescriptionActionsComments
System administrator1. Define the campaign type (project type).
2. Create campaign(s) (projects).
3. Create products.
4. Create product variants.
5. Assign product variants as campaign resources.
6. Create, search, update, and deactivate user accounts.
7. CRUD other system administrator accounts.
8. Create, assign, update, and delete role assignments.
9. Create, assign, update, and delete campaign assignments.
10. Define MDMS configurations (including the project type).
11. Create localisation.
12. Create, search, edit, and delete checklists.
13. Assign checklists to projects.
14. Edit/delete filled checklists.
15. Boundary setup.
RegistrarA frontline worker (FLW) who is responsible for registering households. The registrar also shares awareness messages (SBCC).1. Create a new household.
2. Create a new individual.
3. Map individuals to households.
4. Assign household/individual as the beneficiary of a campaign.
5. Read, update, and delete for all actions mentioned above.
6. View offline reports.
7. Create, and view complaints.
DistributorFrontline worker (FLW) who is responsible for registering households and updating the service delivery details against the registered households. The registrar also shares awareness messages (SBCC).1. Create a new household.
2. Create a new individual.
3. Map individuals to households.
4. Assign a household/individual as the beneficiary of a campaign.
5. Update service delivery against the beneficiary (household/ individual).
6. Read, update, and delete for all actions mentioned above.
7. View offline reports.
8. Create, and view complaints.
Field supervisorResponsible for monitoring the field teams. This user is also responsible for training the FLW teams, monitoring the field team's progress during campaign execution, managing stocks at the community warehouse, and performing random inspections during the campaign execution.1. View assigned checklists.
2. Fill assigned checklists.
National supervisorSupervisors are responsible for overseeing the campaign operations, conducting random and scheduled inspections, filling supervision checklists, supporting field supervisors to tackle operational issues under their jurisdictions, and training users on campaign SOP and digital tools.1. View assigned checklists.
2. Fill out assigned checklists.
3. View completed checklists.
4. Create, search, update and deactivate user accounts (except the system admin).
5. Assign, or update, or delete role assignments.
6. Assign, or update, or delete campaign assignments.
7. View the national-level dashboard page.
8. Select and view the dashboard for each province.
9. View indicators and visualisations district-wise for each province.
10. Drill-down charts to view the metrics upto the lowest boundary level (village).
11. Filter dashboard indicators by the date range.
12. Share dashboard pages/visualisations by email/WhatsApp.
13. Download dashboard pages/visualisations as PDF/JPG.
14. View the offline Excel reports at specified intervals.
15. View the checklists completion rate for the country across all levels of supervisors (national, province, district, and field).
Provincial supervisorSupervisors are responsible for overseeing the campaign operations, conducting random and scheduled inspections, filling supervision checklists, supporting field supervisors to tackle operational issues under their jurisdictions, and training users on campaign SOP and digital tools.1. View assigned checklists.
2. Fill out assigned checklists.
3. View completed checklists.
4. Create, search, update, and deactivate user accounts (except for the system admin).
5. Assign, or update, or delete role assignments.
6. Assign, or update, or delete campaign assignments.
7. View the province-level dashboard page.
8. View indicators and visualisations district-wise for the province.
9. Drill-down charts to view the metrics upto the lowest boundary level (village).
10. Filter dashboard indicators by the date range.
11. Share dashboard pages/visualisations by email/WhatsApp.
12. Download dashboard pages/visualisations as PDF/JPG.
13. View the offline excel reports at specified intervals.
14. View the checklists completion rate for the assigned province across all levels of supervisors (national, province, district, and field).
District SupervisorSupervisors are responsible for overseeing the campaign operations, conducting random and scheduled inspections, filling supervision checklists, supporting field supervisors to tackle operational issues under their jurisdictions, and training users on campaign SOP and digital tools.1. View assigned checklists.
2. Fill out assigned checklists.
3. View completed checklists.
3. Create, search, update, and deactivate user accounts (except for the system admin).
4. Assign/update/delete role assignments.
5. Assign/update/delete campaign assignments.
6. View the district-level dashboard page.
8. View indicators and visualisations, administrative post-wise, for the district.
9. Drill down charts to view the metrics upto the lowest boundary level (village).
10. Filter dashboard indicators by the date range.
11. Share dashboard pages/visualisations by email/WhatsApp.
12. Download dashboard pages/visualisations as PDF/JPG.
13. View offline excel reports at specified intervals.
14. View the checklists completion rate for the assigned district across all levels of supervisors (national, province, district, and field).
Warehouse manager1. Record stock transactions: Create receipt, issues, and returns.
2. View stock reconciliation (system calculated).
3. Submit the reconciliation form.
4. View offline reports for inventory reconciliation.
Programme managerThis user consumes the data collected and shared by the FLW and takes decisions based on the data present. This user must have access to all dashboards with the default view of the data belonging to their jurisdiction and a level below. For example, a provincial manager must be able to view the aggregated data from the entire province as well as the data for individual districts after logging into the system.
Help desk userSupports an executive to resolve, routes complaints raised during the campaign. This user also helps in user management requests.1. Create, view complaints.
2. Resolve complaints, assign complaints, and reject complaints.
3. Create, search, update, and deactivate user accounts (except for the system admin).
4. Assign/update/delete role assignments.
5. Assign/update/delete campaign assignments.

--- # 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/specifications/role-action-mapping.md?ask=&goal= ``` `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.