> 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/beneficiary-id.md).

# Beneficiary ID

## Overview

The Beneficiary ID feature enables the reuse of beneficiary registries across campaigns by assigning a unique, reusable ID to each household or individual.

It helps CDDs easily identify beneficiaries during follow-up visits, reducing duplicate records, lowering operational overhead, and ensuring consistency in the database, especially in contexts without a universal national ID system.

## Key Features

* Unique ID Assignment: Pre-generated Beneficiary IDs are created on the server and synced to the app during login, and these IDs are unique across the campaign.
* Offline Access: IDs remain accessible in the app even without internet after login.
* Registry Reuse: The same IDs can be used across multiple campaigns and acts as a permanent ID for the beneficiary.

## **User Roles**

<table><thead><tr><th width="119.109375">Role</th><th width="247.5">Scope of action</th><th>Role description</th></tr></thead><tbody><tr><td>Distributor</td><td>Distributor generates the required beneficiaries IDs for distribution.</td><td>While the Distributor registers a household , a unique beneficiary ID is assigned and this ID can be used to search the household at later point of time as well</td></tr></tbody></table>


---

# 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/beneficiary-id.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.