> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/pbms/_archive/previous-generation/functionality/beneficiary-management/beneficiary-registry/user-guides/assign-a-program-to-a-group.md).
# Assign a Program to a Group
This document provides instructions to assign a program to a group.
## Prerequisites
* The user must have Registrar and Administrator role.
* The user must have access to the Beneficiary Registry module in OpenG2P systems.
## Procedure
1. Click the main menu icon  and select ***Registry***.
***Registry*** screen is displayed.
The group names are listed below the ***Name*** column.
2. Click the group name which has to be assigned to a program.
For example, here the group name "Family Group" is selected.
***Groups/Family Group*** screen is displayed.
3. Click the ***Action*** button and select ***Add to Program***.
***Add to Program*** screen is displayed.
4. Select the appropriate program from the drop-down.
or
5. Select the ***Search More.***
***Search: Program*** screen is displayed.
6. Search for the appropriate program or click the program below the ***Name*** column.
The program name is displayed in the ***Program*** drop-down.
7. Click the ***Assign*** button to assign the program to a group.
8. Click the ***Cancel*** button to exit from the screen.
For example, you can find the newly assigned program listed in the ***Program*** tab in the ***Family Group*** screen.
---
# 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.openg2p.org/products/pbms/_archive/previous-generation/functionality/beneficiary-management/beneficiary-registry/user-guides/assign-a-program-to-a-group.md?ask=&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.
