> For the complete documentation index, see [llms.txt](https://help.steeple.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.steeple.com/en/mises-a-jour-produit/semaine-2026-02-23.md).

# Week of 23/02/2026 — Separation of notifications/activities and message tracking

## Notifications — Separation of notifications and activities

Personal notifications and community activities were grouped in the same space, which could harm readability and make it harder to identify priority items. This change aims to **clarify the information**, better distinguish personal interactions from community news and improve the management of unread items.

### 🆕 What has been updated

* **New “Activities” page** : creation of a dedicated space to view notifications related to community activities.
* **Simplified navigation** : two separate tabs — *“My notifications”* and *“Activities”* — for clearer reading.

<figure><img src="/files/80f2178d998f046887b6d074237ba0733b44803e" alt=""><figcaption></figcaption></figure>

## Messaging — Improved message read tracking and reaction tracking

Users needed better visibility into the delivery of their messages, especially for important communications. It was difficult to quickly identify who had or had not read a message. This change aims to **make read tracking clearer, more reliable, and more accurate**.

In addition, it is now possible to see who reacted to a message simply by **hovering over the emoji** with \[...].

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


---

# 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.steeple.com/en/mises-a-jour-produit/semaine-2026-02-23.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.