# Device Notifications

### Creating a Device Notification

Email notifications are configured on the platform under **Devices → Settings** tab.

1. In the **Notifications** section, click **Create** to add a new template and assign it a name.
2. Use the dropdown menus to select the desired **types** (Error, Information, Warning) and **categories** (Devices, Player, Licensing).
3. Based on the selected types and categories, choose the **triggers** on which you want to be notified (e.g., when the card dispenser is running low, a paper jam occurs, etc.).
4. In the **Groups** and **Devices** fields, select the specific endpoints you want to monitor.
5. For the **sending method**, you can choose between:
   * **Email** – a separate email is sent for each event
   * **Email Report** – a summary report is generated and sent according to a schedule defined by a Cron expression
6. In the **Recipients** field, select one or more users who should receive the notifications.
7. Finally, **save the template** to complete the setup.

{% hint style="info" %}
You can create multiple email notification rules depending on the devices being monitored (e.g., by location) or the type of issue (e.g., software or hardware).
{% endhint %}

<figure><img src="/files/GXFpPSGA9XbXBWav0I5Q" alt=""><figcaption></figcaption></figure>

### Modifying Notification Subjects

In the **Email Subjects** section, you can customize the notification subject lines per trigger and in either of your available languages.

{% hint style="info" %}
Using placeholders, such as {DeviceName} and {CurrentStatus}, helps you get a quick overview of issues without opening each notification email.
{% endhint %}

<figure><img src="/files/lAx8CZzIHyB1AZhlWEAf" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.friendlyway.com/device-management/device-notifications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.