> For the complete documentation index, see [llms.txt](https://docs.aohwv.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aohwv.dev/administration/notifications.md).

# Notifications

The Notifications page is where you manage email notification templates, delivery schedules, and send logs for your AOH Sync environment.

![The Notifications page showing a "Notification server — 404 page not found" banner with an Unreachable status badge, three tabs (Templates, Schedules, Logs), and a Templates panel listing example template cards](https://2706226485-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F8BF8xXbTZGWilkpjaGNh%2Fuploads%2Fgit-blob-798e2b72883f34f16d578b6267c1c77ce4b6e69a%2Fnotifications.png?alt=media)

*The Notifications page with three tabs: Templates, Schedules, and Logs. The notification server status banner appears at the top of the page.*

{% hint style="warning" %}
If the notification server is unavailable, a status banner at the top of the page shows **Unreachable**. Templates and schedules are still visible, but email delivery is paused until the server is reachable again.
{% endhint %}

## What you can do here

| Action            | What it does                                                                                                                                                         |
| ----------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Templates tab** | View and search the global email templates available across your notification server. Templates are created and edited by administrators on the notification server. |
| **Schedules tab** |                                                                                                                                                                      |
| **Logs tab**      |                                                                                                                                                                      |
| Search templates  | Use the search box on the Templates tab to find a template by name or slug.                                                                                          |

## How to use it

{% stepper %}
{% step %}
**Check server status** Confirm the notification server status banner at the top of the page shows no error. If the server is **Unreachable**, contact your administrator — email delivery is paused until the server is available again.
{% endstep %}

{% step %}
**Review the available templates** Open the **Templates** tab to see the email templates configured for your environment. Each template card shows its name and a preview of the email body. Templates are created and edited by administrators on the notification server — contact your administrator if a template needs to be added or changed.
{% endstep %}

{% step %}
**Review schedules and logs** Use the **Schedules** tab to confirm when notifications are set to send, and the **Logs** tab to verify recent delivery history.
{% endstep %}
{% endstepper %}

## Related

* [System Settings](/administration/system-settings.md)
* [Audit & Status Logs](/administration/audit-and-status-logs.md)
* [User Management](/administration/user-management.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.aohwv.dev/administration/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.