> 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/platform/portals-and-apps/beneficiary-portal.md).

# Beneficiary Portal

The Beneficiary Portal is a user-friendly website designed specifically for beneficiaries, showcasing the full range of OpenG2P features on a desktop web browser. Its primary purpose is to illustrate OpenG2P’s capabilities from the beneficiary’s perspective, presented through a branded, attractive, and intuitive interface.

This portal integrates all major modules—Registry, PBMS, SPAR, and G2P Bridge—by connecting to each one to provide beneficiaries with the necessary information and processes. Consequently, the portal is intended to be deployed as a single installation per environment or sandbox, rather than one per module. The underlying concepts and design of the portal can also be leveraged for developing a mobile application for beneficiaries.

## Functionality

1. Landing page (without login): OpenG2P branded landing page, highlighting that this is a beneficiary portal (detailed contents TBD)
2. User (beneficiary) login via eSignet
3. Home page like a dashboard post login showing the following:
   1. All the programs that the beneficiary is part of along with their status including the ones she/he has applied but not yet confirmed
   2. All the registries that she/he is part of
   3. User’s current linked bank account (from SPAR)
   4. Total amount of benefit - cash or in-kind - received till date under each scheme
   5. Potential applicable schemes for the user (that she/he has not applied for yet)
   6. Any notifications/broadcast from the system
   7. Any issues with money or in-kind transfer (from G2P Bridge)
4. List of all programs offered by the department and ability to apply for them
5. Application via a form (we can follow our existing self service flow)
6. Ability to update bank account via SPAR
7. View of all the transactions related to money or benefit transfer - history of all benefits received under each scheme she/he is enrolled for.
8. Detailed registry view with ability to update fields (for now let’s have a simple flow as this can get very complex).
9. A separate space for grievance redressal - file a complaint. This would show the list of past complaints and form to file a new one.

## Wireframes

{% embed url="<https://www.figma.com/proto/3hYyBVpNpqSl4PbaXy8rgw/Beneficiary-Portal?node-id=1-2&page-id=0:1&starting-point-node-id=1:2&t[%E2%80%A6]ntent-scaling=fixed>" %}

## Architecture

{% embed url="<https://miro.com/app/board/uXjVJKFLcas=/?share_link_id=553998889894>" %}

## Backend APIs


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.openg2p.org/platform/portals-and-apps/beneficiary-portal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.