> 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-openid-vci-programs.md).

# G2P OpenID VCI: Programs

### Module name

g2p\_openid\_vci\_programs

### Module title

G2P OpenID VCI: Programs

### Technology base

[Odoo](https://www.odoo.com/)

### Functionality

* This module adds a new issuer type called `Beneficiary,`extending the ***G2P OpenID VCI*** module functionality. It effectively adds the ability to issue VC for beneficiaries who are part of a program in PBMS.
* It adds a parameter to attach a Program to an Issuer. With this module, each Program in PBMS is an issuer.
  * For example, if three programs are operating on PBMS, 3 different issuers can be created with issuer\_type as "Beneficiary" and different programs.
    * Configure 3 different scopes for the three issuers. Example:
      * IssuerName: "SafetyNetIssuer", scope: "safety\_net\_program\_vc\_ldp", Program: "Safety Net Program".
      * IssuerName: "HumAidIssuer", scope: "hum\_aid\_program\_vc\_ldp", Program: "Humanitarian Aid Program", etc.
      * If the content of the credential is the same for all the 3 programs, then use a generic credential\_type and format across all three issuers, like "OpenG2PBeneficiaryVerifiableCredential". If the content is different in all programs, use different credential types.
* Unlike a Registry VC, a Beneficiary may contain additional data, like the name of the Program, the duration for which this beneficiary is part of the program, the last date till which this beneficiary is part of the program, etc. This module supports all of these.

Note:

* A credential will only be issued if the sub from auth JWT exists as one of the IDs in the registry against a registry entry, and the registrant is also an enrolled beneficiary of the said program.
* The rest of the functionality from the base module remains the same.

### Source code

<https://github.com/openg2p/openg2p-vci-beneficiary>


---

# 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-openid-vci-programs.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.