> 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/entitlement/user-guides/configure-default-cycle-managers.md).
# Configure Default Cycle Managers
This document provides instructions to configure ***Cycle Managers*** in Program module.
## Prerequisites
* The user must have access to OpenG2P systems.
* The user must have Program Manager 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 Cycle Managers***.
***Cycle Managers*** screen is displayed.
3. Click the ***Create*** button.
***Cycle Managers/New*** screen is displayed.
The fields and their descriptions are given below.
| Field | Description |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Name | Enter the manager name. It is a mandatory field. |
| Program | Select the appropriate Program from the drop-down. It is a mandatory field. |
| Cycle Settings | |
| Auto-approve Entitlements | Check the option, if required. It is an optional field. |
| Approver Group | Select the appropriate option from the drop-down. It is a mandatory field. |
| Recurrence |
Select the appropriate option from the drop-down. The valid values are
Days - Enter the number of days to repeat the cycle of the entitlement.
Weeks - Enter the number of weeks to repeat the cycle of the entitlement.
Months - Enter the number of months to repeat the cycle of the entitlement.
Years - Enter the number of years to repeat the cycle of the entitlement.
|
4. Click the ***Save button*** to save the data and exit the screen.
5. Click the ***Discard*** button to exit the screen without saving the data .
The newly created cycle manger is added in the existing cycle managers list.
### Recurrence - Weeks
4. Select the option ***Weeks*** in the drop-down.
Name of the weeks with check boxes are displayed.
5. Check the appropriate week to repeat the cycle of the entitlement.
### Recurrence - Months
6. Select the option ***Months*** in the drop-down.
***Day of Month*** field is displayed.
7. Select the appropriate option from the drop-down. The valid values are:
* Date of month
* Day of month
This completes the process of configuration of Cycle Managers in the Program module.
---
# 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/entitlement/user-guides/configure-default-cycle-managers.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.
