> 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/facial-recognition/enrol-and-verify-helpers-distributor.md).
# Enrol & Verify Helpers: Distributor
## Overview
Helpers are team members who do not have their own HCM login. They are enrolled and verified on the Distributor’s device under Non-mobile users. Up to two helpers can be supported on a single device. Each helper gets their own face profile linked to their own user ID, stored under the system user’s profile.
{% hint style="info" %}
**Before you start:**
Verify your own face first. A helper cannot be verified until the system user on that device has completed their own scan.
The helper must be physically present. Enrollment captures their face live; it cannot be done from a photo.
Helper enrollment currently requires the system user to be present with the device. Adding a helper mid-campaign is not supported offline.
{% endhint %}
## Steps
### Enrol Helpers
{% stepper %}
{% step %}
#### Open the menu
Tap Non-mobile users. Tap the menu icon at the top left of the home screen. The side menu shows your user QR code, your user ID, Home, View Downloaded Data, and Non-mobile users.
{% endstep %}
{% step %}
#### Find the helper in the list
The Non-mobile users screen lists each helper with their name, age, phone number, and user ID.
{% endstep %}
{% step %}
#### Tap Enrol Face
The guided capture opens. It is the same six-angle sequence used for your own enrollment, with the same on-screen prompts.
{% endstep %}
{% step %}
#### Capture the helper’s face
Hand the phone to the helper or hold it in front of them. Follow the prompts through all six captures.
{% endstep %}
{% step %}
#### Wait for the location capture
Fetching location… appears while GPS coordinates are recorded against the enrollment.
{% endstep %}
{% step %}
#### Verify the result
A green confirmation appears at the bottom of the screen reading Face enrolled for \[helper name], and the button on the helper’s card changes from Enrol Face to Verify Face.
{% endstep %}
{% endstepper %}
### Verify Helpers
{% stepper %}
{% step %}
#### Tap Verify Face on the helper’s card
Available once the helper has been enrolled. If your own verification is outstanding, complete it first.
{% endstep %}
{% step %}
#### Scan the helper’s face
The camera opens and shows Processing… then Scanning… as the face is compared against the helper’s enrolled profile.
{% endstep %}
{% step %}
#### Verify the result
On success, you see Verified! with the match percentage.
{% endstep %}
{% step %}
#### Confirm the card status
The helper’s card now shows a green Verified chip in place of the Verify Face button.
{% endstep %}
{% endstepper %}
{% hint style="info" %}
**Rules that are enforced:**
A helper cannot be enrolled or verified using the system user’s face. The scan will not pass.
Two helpers cannot be enrolled with the same face.
A helper enrolled on one device cannot be verified under a different user’s login.
Helpers who are not mapped to facial recognition will not show a verification history card on the home screen.
{% 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.digit.org/health/access/public-health-product-suite/health-campaign-management-hcm/facial-recognition/enrol-and-verify-helpers-distributor.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.
