> 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/2026/september/new-users-now-see-the-refreshed-interface.md).

# New users now see the refreshed interface

September 7, 2026

From today, all new Channable users will see the **Modern** version of the Channable interface. This follows on from the [announcement](/changelog/2026/august/a-refreshed-channable-interface.md) that we made in August.

The Help Center will document both the **Modern** and **Legacy** versions of the interface during the transition, so be sure to check that you're following the correct instructions. They'll be labelled clearly in each article.

{% hint style="info" %}

#### Are you an existing user and still on the 'Legacy' UI?&#x20;

We recommend [switching to the Modern UI](/changelog/2026/august/a-refreshed-channable-interface.md#how-to-switch) for the best experience.
{% 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/2026/september/new-users-now-see-the-refreshed-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.
