> For the complete documentation index, see [llms.txt](https://docs.kiloiot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiloiot.io/dashboards/organizing-dashboards.md).
# Organizing Dashboards
Organize many Kilo IoT dashboards into folders with drag-and-drop reordering — multi-site deployments stay scannable.
As your deployment grows, so does your collection of dashboards. A handful of dashboards is easy to scan in the sidebar, but when you're managing views across multiple buildings, floors, and teams, a flat list becomes unmanageable. Folders let you group dashboards by site, purpose, or team — and drag-and-drop reordering lets you put the most critical views at the top.
## Opening the dashboard management modal
Click the **gear icon** (tooltip: **"Dashboard settings"**) next to the Dashboards section in the sidebar. The management modal opens with the title **"Dashboard settings"** and the subtitle **"Create folders and rearrange dashboards and folders with a drag-and-drop gesture"**.
If you have no dashboards yet, the modal displays **"No dashboards yet"** in the center.
## Creating a folder
At the top of the management modal, a text input lets you create a new folder:
1. Enter a folder name. The placeholder reads **"My folder"**.
2. Click **Create folder**.
If you leave the name blank and try to create, the validation message **"Folder name is required"** appears.
Folders appear in the sidebar as expandable groups. Click a folder to expand it and see the dashboards inside.
### Folder structure
The folder system supports **one level of nesting** — folders can contain dashboards, but folders cannot contain other folders. This keeps the hierarchy flat and predictable:
```
Dashboards
├── Building A (folder)
│ ├── Temperature Overview
│ └── Cold Chain Compliance
├── Building B (folder)
│ └── HVAC Monitoring
└── Executive Summary (top-level dashboard)
```
## Reordering with drag-and-drop
The management modal displays all your dashboards and folders in a tree view. You can drag items to:
* **Reorder** dashboards and folders within the list.
* **Move a dashboard into a folder** by dragging it onto the folder.
* **Move a dashboard out of a folder** by dragging it to the root level.
Changes are reflected immediately in the sidebar ordering.
## Deleting a folder
To delete a folder from the management modal, click the **delete icon** (trash) next to the folder name. A confirmation dialog appears:
**"Are you sure you want to delete {folder name} folder?"**
with the warning:
**"All dashboards inside this folder will also be deleted. Once deleted, this action cannot be undone."**
Click **Yes, delete** to confirm. This removes the folder and every dashboard it contains permanently.
## Deleting a dashboard from management
Individual dashboards can also be deleted from the management modal. The confirmation reads:
**"Are you sure you want to delete {dashboard name} dashboard?"**
**"Once deleted, this action cannot be undone."**
Click **Yes, delete** to confirm.
## Closing the modal
Click **Ok** to close the management modal. All changes to folder structure and ordering are already applied.
## Naming conventions for multi-site operations
A few conventions help teams navigate large dashboard collections:
* **Name folders by location** — "Building A", "Warehouse East", "DC-Frankfurt". This maps directly to physical sites.
* **Name dashboards by function** — "Temperature Overview", "Access Monitoring", "Energy Consumption". Function-based names stay useful even as devices change.
* **Avoid generic names** — "Dashboard 1" or "Test" become impossible to identify at scale.
## Related pages
* [Creating Dashboards](/dashboards/creating-dashboards.md) — Create the dashboards that go into your folders.
* [Adding Widgets](/dashboards/adding-widgets.md) — Populate dashboards with device data.
---
# 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.kiloiot.io/dashboards/organizing-dashboards.md?ask=&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.
