> 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.1/beneficiary-management/notifications.md).

# Notifications

## Introduction

Notifications to beneficiaries and administrators are a must, especially when there are multiple stages of a delivery chain, usually with long time intervals between the different stages. Beneficiaries must be notified of their enrollment status, entitlements, payouts, exits, etc. Multiple channels such as SMS, email, and messaging apps can be used for notifications.

OpenG2P provides configuration of email, SMS, and Fast2SMS notifications in a few simple steps. Depending on the implementation needs of a program, notifications can be triggered for specific events in the delivery chain.

The figure below shows example notifications configured for two events - enrolling in the program and sending OTP.

<figure><img src="https://1098398587-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYPoyCjtgyun9HOF3pnQT%2Fuploads%2FtY4AaKli8BuBVOKAArZW%2Fnotification-events.png?alt=media&amp;token=e42fbef8-8570-45e4-b367-6605f3ec396a" alt=""><figcaption></figcaption></figure>

## Notification Manager

OpenG2P manages notifications via Notification Managers. Each program has at least one Notification Manager configured. The platform defines a different Notification Manager for each type of notification - SMS, email, Fast2SMS. These are the most commonly used Notification Managers:

* SMS Notification Manager
* Email Notification Manager
* Fast2SMS&#x20;

OpenG2P uses the in-built [Qweb Templates](https://www.odoo.com/documentation/16.0/developer/reference/frontend/qweb.html) and [Inline Templates](https://apps.odoo.com/apps/modules/10.0/mail_inline_css/) for configuring the HTML pages and fragments. Notifications are sent based on the event and application configurations.

<figure><img src="https://1098398587-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYPoyCjtgyun9HOF3pnQT%2Fuploads%2FRcTHijphASCngq9QUBmM%2Fnotification-template.png?alt=media&amp;token=6ce6318d-bc9d-4261-9f7b-c461505585c1" alt=""><figcaption></figcaption></figure>

## Configuring notifications

Configuring the notifications requires two steps:

#### Create a Notification Manager type

The program administrator must create at least one Notification Manager for each Notification Manager type required. To learn more about this step, click [here](/1.1/guides/user-guides/create-notification-manager-types.md).

#### Add the Notification Manager to a program

The program administrator needs to add the Notification Manager(s) created in the first step to the program. To learn more about this step, click [here](/1.1/guides/user-guides/configure-notification-manager.md).&#x20;

## Send notifications

Sending the notifications is a one-click operation. Based on the state of the program - enrolment, entitlement, payment, etc. - the corresponding notification is sent by the Notification Manager types configured for the program. To learn more about this step, click [here](/1.1/guides/user-guides/send-notifications-to-individual-registrants.md).

## How-To Guides

[Create Notification Manager Types](/1.1/guides/user-guides/create-notification-manager-types.md)

[Create Notification Manager under Program](/1.1/guides/user-guides/configure-notification-manager.md)

[Send Notifications to Individual Registrants](/1.1/guides/user-guides/send-notifications-to-individual-registrants.md)


---

# 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.1/beneficiary-management/notifications.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.