> For the complete documentation index, see [llms.txt](https://help.glpi-project.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.glpi-project.org/glpi-12/setup/notifications.md).

# Notifications

GLPI has a notification feature that allows it to send messages following an event in the application, to users via email, browser notifications, and other methods (expandable by plugins).

GLPI comes with notification definitions pre-defined and they can be used out of the box right away after enabling notifications.

To do this, you must activate the **Enable followup** option then **Enable followup via email** or **Browser followups from browser** to display the settings menu:

* [Definitions](https://help.glpi-project.org/glpi-12/setup/notifications/definitions.md)
* [Templates](https://help.glpi-project.org/glpi-12/setup/notifications/templates.md)
* [Template example](https://help.glpi-project.org/glpi-12/setup/notifications/template_example.md)
* [Email notifications](https://help.glpi-project.org/glpi-12/setup/notifications/email_notifications.md)
* [Alarm options](https://help.glpi-project.org/glpi-12/setup/notifications/alarm_options.md)

{% hint style="info" %}
Notifications work as follows (*e.g.: ticket creation notified by email*):

1. The ticket is created in GLPI.
2. GLPI looks for notifications of the "**ticket creation**" event in the ticket entity (otherwise in the parent entities).
3. GLPI builds the list of recipients according to the settings.
4. For each recipient, GLPI generates the mail in the language of the user if the translation exists, otherwise it is the "**Default translation**".
5. The emails are placed in **Administration > Notification queue** waiting to be sent by the automatic task `queuednotification`.
   {% endhint %}

{% hint style="warning" %}
When new notifications are added to GLPI through an update, they are enabled by default.
{% endhint %}


---

# 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://help.glpi-project.org/glpi-12/setup/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.
