> 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/hcm-ui-configuration/project-selection.md).

# Project Selection

## Overview

Once a user logs into the HCM app, the project selection screen displays all the projects assigned to the user.

***

### 📋 1. Workflow Details

* **Project Screen**: Displays a list of projects assigned to the user. The user selects the project from the list to view.

<div align="left"><figure><img src="https://content.gitbook.com/content/I0KFbSBTySIQ7TCOKnJF/blobs/o1vmZeeNilu2I3dzNuTJ/image.png" alt="" width="205"><figcaption></figcaption></figure></div>

<div align="left"><figure><img src="https://content.gitbook.com/content/I0KFbSBTySIQ7TCOKnJF/blobs/PQSBMADdOccTgP2eYzub/image.png" alt="" width="205"><figcaption></figcaption></figure></div>

* **Data Sync**: App fetches and syncs data for the selected project only.
* Sync occurs automatically at each login, so a stable internet is required at the start of the day before fieldwork.
* A “Sync in Progress” window appears on the screen, and the user cannot perform any other action until the process is complete..

***

### ⚙️ 2. Technical Implementation

#### 2.1 UI Components

* **DigitProjectCell**: Used to display each project row in the list.
* **DigitElevatedButton**: Use the “Continue” button to confirm the selection.
* **Toast Notifications**: Used to display success/error messages via DigitToastHelper.

#### 2.2 Code References

* Project selection screen: <https://github.com/egovernments/health-campaign-field-worker-app/blob/master/apps/health_campaign_field_worker_app/lib/pages/project_selection.dart>
* UI components imported from:\
  `digit_components/lib/widgets/digit_project_cell.dart`,\
  `.../digit_elevated_button.dart`,\
  `.../atoms/digit_toast_helper.dart`&#x20;

***

### 🔄 3. API Role Action Mapping

| Action                 | Endpoint                         | Purpose                                                                        |
| ---------------------- | -------------------------------- | ------------------------------------------------------------------------------ |
| Fetch user projects    | `POST /project/staff/v1/_search` | Fetches projects linked to the logged-in staff (using staffId).                |
| Fetch project metadata | `POST /project/v1/_search`       | Retrieves detailed project info such as `tenantId`, `name`, and `projectType`. |

* **Auth**: Requires `RequestInfo.authToken`.
* **Payload Example (staff search)**:

  ```json
  {
    "RequestInfo": { "authToken": "string" },
    "ProjectStaff": { "staffId": "string" }
  }
  ```
* **Payload Example (project metadata)**:

  ```json
  {
    "RequestInfo": { "authToken": "string" },
    "Project": [
      { "tenantId": "tenantA", "name": "string", "projectType": "string" }
    ]
  }
  ```
* **Role mapping**: Projects returned here determine what app screens and data the user can access post-selection.


---

# 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/hcm-ui-configuration/project-selection.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.
