> For the complete documentation index, see [llms.txt](https://docs.akenza.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akenza.io/dashboard-builder/managing-dashboards/dashboard-groups.md).

# Dashboard Groups

#### Creating Groups

To create a new group click on the context action button of the Dashboards group and select *Create Group*

By default all new dashboards are created outside of any existing group you might have, unless you create them from the groups context action in the sidebar or on the *Overview* page

#### Toggling Groups

To focus you can collapse groups in the side nav or on the overview page to hide dashboards. Both display states are synched.

#### Renaming Groups

To change the default name of a group click on the groups context action button and select *Rename* *Group* in either the sidebar or on the *Overview* page


---

# 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://docs.akenza.io/dashboard-builder/managing-dashboards/dashboard-groups.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.