> 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-05-04-1.md). # Week of 04/05/2026 — Dynamic community administrator / Directory: new filters ### **Dynamic communities – Assigning the administrator role** Until now, the administrator role could not be assigned to a collaborator on a manual community. Now it is also possible for dynamic communities. 🆕 What has been updated * **Targeted visibility** : only dynamic communities of which the user is already a member are suggested for role assignment, thus avoiding management errors. * **Visual indicator** : addition of a “Dynamic community” label to quickly identify the type of community involved.
### Directory — A refocused view on the right contacts In organizations with many communities, the directory displayed all collaborators without the ability to target those you actually work with. This development aims to provide the option to filter by scope and more quickly find the right people. #### 🆕 What has been updated * **Multi-criteria filters** : addition of filters by communities, departments, and locations to see only the relevant collaborators according to your scope of work.
--- # 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-05-04-1.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.