> 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/doc-plugins/plugin-glpi-network/unread.md).

# Unread messages

## Requirements (self-hosted)

| GLPI Version | Minimum PHP | Recommended |
| ------------ | ----------- | ----------- |
| 10.0.x       | 8.1         | 8.2         |
| 11.0.x       | 8.2         | 8.4         |

{% hint style="info" %}
A [GLPI Network BASIC](https://services.glpi-network.com/#offers) subscription (or higher) is required. This plugin is also available for all GLPI Network [Cloud instances](https://glpi-network.cloud).
{% endhint %}

***

## Install the plugin

* Go to the marketplace. Download and install the plugin **Unread messages**.

<div align="left"><figure><img src="/files/F4s4RkbHq0PCKME5NE3h" alt="images/Unread-1.png"><figcaption></figcaption></figure></div>

***

## Setting up the plugin

* Go to **Administration > Entities**, **unread messages** tab

There are 3 possible settings:

| Operation                           | Effect                                                                                                                                                                                                                                      |
| ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Disabled**                        | The plugin will remain inactive                                                                                                                                                                                                             |
| **Per user helpdesk;share central** | Users with the self-service profile will be notified of tickets for which they are the requestor. Technicians, for their part, will share the notifications. If a notification is read, it will be marked as read for all other technicians |
| **Per user**                        | Each user will have access to their own queue of notifications, including those for their group and their individual assignments                                                                                                            |

### Notify actor types

When the mode is set to **Per user**, the **Notify actor types** field is mandatory. It defines which actor roles on a ticket will receive unread message notifications.

| Value          | Description                            |
| -------------- | -------------------------------------- |
| **Requester**  | The user(s) who opened the ticket      |
| **Observer**   | Users added as observers on the ticket |
| **Technician** | Users assigned to the ticket           |

Multiple values can be selected. If this field is left empty, **no notifications will be generated**, even if the mode is active.

{% hint style="warning" %}
Leaving **Notify actor types** empty while using the **Per user** mode silently disables notifications. Always select at least one actor type to ensure the plugin operates as expected.
{% endhint %}

***

## Display notifications

### Header

When a new activity has not yet been viewed, a **bell icon** appears:

<figure><img src="/files/iRyVy1pfaSITk2hKsJiB" alt="images/Unread-2.png"><figcaption></figcaption></figure>

### Listed

Unread messages on a ticket highlight the ticket concerned and a red indicator :

<figure><img src="/files/3tULPjYZDo51qqtEaYn1" alt="images/Unread-3.png"><figcaption></figcaption></figure>

### Ticket timeline

New messages will be identified by a banner **New messages**.

<figure><img src="/files/PhvJ135T9yNohVKfCatK" alt="images/Unread-4.png"><figcaption></figcaption></figure>

### Management by entity

Management by entity is possible to manage the counting of notifications by entity.

* Go to **`Administration`** > **`Entities`**, and select the desired entity.
* In the **Unread messages** tab, select the option that suits you so that unread messages behave differently to the parent entity.

<figure><img src="/files/35VSMeLAYAZ1rgWbvUQv" alt="images/Unread-5.png"><figcaption></figcaption></figure>

***

## FAQ

If you have any questions about using the plugin, please consult our FAQ

<a href="/spaces/SvoJ3lioglS2UZLcWWyP/pages/EiiRIeGGTb6g8Hbtw3Ih" class="button secondary">Go to FAQ</a>


---

# 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://help.glpi-project.org/doc-plugins/plugin-glpi-network/unread.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.