> 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/platform-services/notification.md).

# Notification

OpenG2P uses a **notification layer** for templates, workflows, multi-channel delivery, and the in-app Inbox. Product services emit business events; they do not implement notification infrastructure themselves.

The integration is one library, `openg2p-notification-connector`, with two folders:

* **`notification-backend-lib`** — OpenG2P Backend services (for example Registry, PBMS, IAM, AWE) call `send()` in-process to trigger events.
* **`notification-ui-lib`** — OpenG2P UI consumes the notification layer's REST APIs and WebSocket for the Inbox. Application screens do not import a notification-layer SDK.

The architecture is independent of any one product. The layer behind the connector can be Novu, SuprSend, or a custom implementation.

See [Notification Architecture](/platform/platform-services/notification/notification-architecture.md) for the contract, package boundaries, and layer abstraction.


---

# 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/platform-services/notification.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.