> 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-03-09.md).

# Week of 09/03/2026 — Shortcuts application and multi-broadcast

## Shortcuts — Application available to everyone

Employees use many tools in their daily work (business software, HR portals, works council sites, IT support…). Access is often scattered across different links or platforms, which makes them harder to use. This change aims to **centralize access to work tools directly in Steeple** and make it easier to distribute them to the right teams.

### 🆕 What has been updated

* The application **Shortcuts is now available to all users**.
* Administrators can **easily create shortcuts** to tools or useful links.
* Shortcuts can be **shared with specific communities**so that only the relevant teams have access to them.
* Employees receive **a notification when a new shortcut is created**so they are immediately informed of the new available access.

👉 Employees therefore have **a single entry point to their work tools**accessible directly from Steeple.

### News — Multi-distribution management

Until now, a post could only be distributed in a single section, forcing administrators to recreate multiple posts to reach different audiences. This change aims to **simplify content distribution**save time in publishing and improve the consistency of communications.

**🆕 What has been updated**

* Ability to **publish a post in several sections simultaneously**.
* New selection interface with **checkboxes and visual preview of the selected sections**.
* Improved user tracking with **alert messages (toasts)** to inform users about the status of drafts and video processing.

### **Community filter – Improved organization and sorting**

When the number of communities increases, their display can become hard to read, especially in the user manager. This change aims to **clarify the organization of communities** and make them easier for administrators to view and manage.

**🆕 What has been updated**

* Implementation of a **clear display hierarchy** of communities:
  1. **Parent community**
  2. **Manual communities**
  3. **Dynamic communities**
* Sorting **alphabetical within each category** for simpler and more readable navigation.

### **Messaging – Notifications for emoji reactions**

\
Emoji reactions are often used to quickly respond to a message (agreement, thanks, approval…). However, users were not always notified when a reaction was added to their messages. This change makes it possible to **better track interactions** and stay informed even without checking the conversation continuously.

**🆕 What has been updated**

* **Real-time notifications on the Web** when a user adds an emoji reaction to one of your messages.
* **Smart notification management** : they are grouped to avoid clutter and update if a user changes their emoji.


---

# 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-03-09.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.