> 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/developer-zone/odoo-modules/g2p-program-approval.md).

# OpenG2P Program: Approval

### Module name

g2p\_program\_approval

### Module title

OpenG2P Program: Approval

### Technology base

Odoo

### Functionality

* The OpenG2P Program Approval module extends the functionality of G2P programs by introducing features related to entitlement approval. Users can manage entitlements efficiently through custom views and benefit from automatic sequence configuration.
* **Sequence Configuration**: Automatic configuration of sequences for entitlements.
* **Security Settings**: Fine-grained security settings using the provided CSV file.
* **Views**: Custom views for entitlement management.

### Design notes

### Relationships with other entities

None

### Dependencies

Module Dependencies

* openg2p\_programs

### User interface

### Configuration

### Source code

<https://github.com/OpenG2P/openg2p-program/tree/15.0-develop/g2p_program_approval>

### Installation

1. Ensure that the `g2p_programs` module is installed as it is a dependency for this module.
2. Install the OpenG2P Program: Approval module from the Odoo Apps interface.
3. After installation, configure entitlement sequences and review security settings.


---

# 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/developer-zone/odoo-modules/g2p-program-approval.md?ask=<question>&goal=<user_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.