> 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/faq/plugins/unread-messages.md). # Unread messages *** ### How to configure **`unread`**? A [procedure](/doc-plugins/plugin-glpi-network/unread.md) is available to help you install the plugin. *** ### What is the **`unread`** feature? Thanks to **`unread`** you will no longer miss a single message from GLPI. When new activity takes place on your instance, a will appear to inform you that a new unread notification is available. *** ### What is the difference between **`Per user helpdesk;shared central`** and **`Per user`** * **`Per user helpdesk;shared central`**: users with the self-service profile will be notified of tickets of which they are the requesters. The technicians, for their part, will share the notifications. If a notification is read, it will be marked read for all other technicians. * **`By user`**: each user will have access to their own notification queue including those of their group and their individual assignments. *** ### Can we have unread message behavior from one entity to another? Yes. This can be configured in **`administration`** > **`entities`**. Choose the entity that suits you and make the necessary settings in the **`unread`** tab. --- # 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/faq/plugins/unread-messages.md?ask=&goal= ``` `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.