> For the complete documentation index, see [llms.txt](https://docs.akenza.io/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/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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.akenza.io/akenza.io/dashboard-builder/managing-dashboards/dashboard-groups.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.