> 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/1.3/pbms/functionality/program-management/user-guides/configure-default-program-manager.md).
# Configure Default Program Manager
This document provides instructions to configure default program manager in the program module.
## Prerequisites
The user must have the Program Administrator role.
## Procedure
1. Click the main menu icon  and select ***Programs***.
***Programs*** screen is displayed.
2. Click the ***Configuration*** in the menu bar and then select ***Default Program Managers***.
***Program Managers*** screen is displayed.
3. Click the ***Create Program*** button.
***Program Managers/New*** screen is displayed.
The fields and their descriptions are given below.
| Field | Description |
| ------------------- | -------------------------------------------------------------------------------------- |
| Name | Enter the program manager name. It is a mandatory field. |
| Program | Select the appropriate program from the drop-down. It is a mandatory field. |
| Number of cycles | Enter the number of cycles on which the entitlements are allocated to the beneficiary. |
| Is Cycleless | Check the option, if required. |
| Copy pervious cycle | Check the option to repeat the pervious cycle configuration. |
3. Click the ***Save*** button to save the data and exit from the screen.
4. Click the ***Discard*** button to exit from the screen without saving the data.
The newly configured program manager is listed in the program managers list.
---
# 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/1.3/pbms/functionality/program-management/user-guides/configure-default-program-manager.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.
.png?alt=media)
.png?alt=media)
