> For the complete documentation index, see [llms.txt](https://developers.make.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.make.com/white-label-documentation/release-notes/release-2026.01-product-improvements.md).

# Release 2026.01-Product improvements

#### **Move scenarios to folders from the scenario page**

You can now move your scenarios to a different folder directly from the scenario page. Select the **Options (⋯)** menu and choose **Move to folder…** to organize your scenarios without leaving the page.

You can keep your scenarios structured and manage them across folders more easily as your projects grow.

#### **Customize columns in the scenario history table**

You can now choose which columns are visible in the scenario history table. Use the column selector to show or hide specific fields and adjust the table to your needs.

This helps you focus on the most relevant information when reviewing scenario runs and makes it easier to analyze performance and troubleshoot issues.

#### Hidden active scenarios card

The **Active scenarios** card is now hidden when you don’t have any active scenarios. Your dashboard stays cleaner and shows only relevant information based on your current setup.


---

# 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://developers.make.com/white-label-documentation/release-notes/release-2026.01-product-improvements.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.
