> 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-de/2026/september/agentur-nutzer-sehen-jetzt-standardmassig-die-modern-oberflache.md).

# Agentur-Nutzer sehen jetzt standardmäßig die Modern-Oberfläche

23\. September 2026

Von 23. September an sehen Agency-Nutzer die **Modern-Oberfläche** standardmäßig. Sie bietet eine klarere Projektübersicht und eine einfachere Navigation zwischen Unternehmen, Einstellungen und Support.

Lies [unsere Einführung in die überarbeitete Channable-Oberfläche](/changelog/changelog-de/2026/august/eine-uberarbeitete-channable-oberflache.md) für einen geführten Rundgang durch die Änderungen. Sie umfasst die aktualisierte Projektansicht, die vereinfachte Navigation und das Agency Dashboard.

{% hint style="info" %}

#### Wenn nötig, zurückwechseln

Du kannst [zwischen der Modern- und Legacy-Oberfläche wechseln](/changelog/changelog-de/2026/august/eine-uberarbeitete-channable-oberflache.md#how-to-switch) bis die Modern-Oberfläche für alle Nutzer Pflicht wird.
{% 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-de/2026/september/agentur-nutzer-sehen-jetzt-standardmassig-die-modern-oberflache.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.