> For the complete documentation index, see [llms.txt](https://helpcenter.channable.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpcenter.channable.com/changelog/changelog-fr/2026/september/les-utilisateurs-dagence-voient-desormais-linterface-modern-par-defaut.md).

# Les utilisateurs d'agence voient désormais l'interface Modern par défaut

23 septembre 2026

A partir du 23 septembre, les utilisateurs Agency voient l’ **interface Moderne** par défaut. Elle offre une Vue d'ensemble plus claire du projet et une navigation plus simple entre les entreprises, les Paramètres et l’assistance.

Lisez [notre introduction A l’interface Channable rafraîchie](/changelog/changelog-fr/2026/aout/une-interface-channable-actualisee.md) pour une visite guidée des changements. Elle couvre la vue du projet mise à jour, la navigation simplifiée et le Panorama Agency.

{% hint style="info" %}

#### Revenez en arrière si nécessaire

Vous pouvez [basculer entre les interfaces Moderne et Legacy](/changelog/changelog-fr/2026/aout/une-interface-channable-actualisee.md#how-to-switch) jusqu’à ce que l’interface Moderne devienne Obligatoire pour Tous les utilisateurs.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://helpcenter.channable.com/changelog/changelog-fr/2026/september/les-utilisateurs-dagence-voient-desormais-linterface-modern-par-defaut.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.