> For the complete documentation index, see [llms.txt](https://docs.mosip.io/1.2.0/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mosip.io/1.2.0/setup/cookbook/training.md).

# Training

## Functional Training and Real-Life Scenarios

Training is the heart of the pilot. The country team is functionally trained through hands-on sessions, and they go through real-life examples during the pilot and how to deal with them.

### Training streams

| Stream                           | Topics                                                                                                                                    | Audience                        |
| -------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- |
| Technical training               | Architecture, deployment, configuration, monitoring and incident response.                                                                | Country technical team          |
| Functional training              | Pre-registration, registration packet flow, ID processing, ID issuance, Lost ID issuance, ID update, eSignet, INJI Wallet, admin console. | Program managers and tech leads |
| Operator and supervisor training | End-to-end registration on the kit, exception handling, daily run-sheet, device hygiene.                                                  | Field operators and supervisors |
| Adjudicator training             | Manual adjudication console, decision rationale, escalation paths.                                                                        | Adjudicators                    |
| Helpdesk training                | Stuck packets, lost credentials, biometric exceptions, complaint logging.                                                                 | Backoffice and Helpdesk staff   |

### Real-life scenarios to walk through

1. A senior citizen with worn fingerprints --- fall back to iris, then to OTP authentication.
2. An infant accompanied by a guardian --- biometrics deferred, guardian linkage captured, consent recorded.
3. A resident with no fingers --- exception biometric flow, missing-biometric reasons captured, supervisor approval.
4. A resident in a wheelchair --- accessibility set-up at the Center, photo booth at seated height, operator script.
5. A resident living in a low/no-connectivity area --- offline registration, packet sync the next morning, status check.
6. A duplicate detection at ABIS --- manual adjudicator reviews the case and decides whether to confirm or reject the duplicate.
7. A lost or damaged ID --- physical re-issuance at the registration center and re-download into a new INJI Wallet device.
8. An impersonation attempt at the relying-party portal --- biometric authentication fails and the helpdesk logs the incident.

{% hint style="info" %}
**Make training stick** Pair every classroom session with a live registration of a real participant (operator, supervisor or technical team member volunteering). Theory alone never produces confident operators.
{% endhint %}


---

# 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.mosip.io/1.2.0/setup/cookbook/training.md?ask=<question>&goal=<endgoal>
```

`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.