> 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-nl/2026/september/gebruikers-van-bureaus-zien-nu-standaard-de-modern-interface.md).

# Gebruikers van bureaus zien nu standaard de Modern-interface

23 september 2026

Vanuit 23 september zien Agency-gebruikers standaard de **Modern** interface standaard. Het biedt een duidelijker projectoverzicht en eenvoudigere navigatie tussen bedrijven, Instellingen en support.

Lees [onze introductie Naar de vernieuwde Channable-interface](/changelog/changelog-nl/2026/augustus/een-vernieuwde-channable-interface.md) voor een begeleide tour van de wijzigingen. Het behandelt de bijgewerkte projectweergave, gestroomlijnde navigatie en Agency Dashboard.

{% hint style="info" %}

#### Schakel terug als dat nodig is

Je kunt [schakelen tussen de Modern en Legacy interfaces](/changelog/changelog-nl/2026/augustus/een-vernieuwde-channable-interface.md#how-to-switch) tot de Modern-interface Verplicht wordt voor alle gebruikers.
{% 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-nl/2026/september/gebruikers-van-bureaus-zien-nu-standaard-de-modern-interface.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.