> 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/creating-dashboards.md).
# Creating Dashboards
Create, rename, and delete Kilo IoT dashboards — named containers that hold widgets for data, charts, and floor plans.
Every monitoring view in the Kilo IoT Server starts as a dashboard. A dashboard is a named container that holds widgets — the visual components that display device data, charts, and floor plans. Before you can add widgets, you need a dashboard to put them in.
This page covers creating new dashboards, editing their metadata, and deleting dashboards you no longer need. For folder management and drag-and-drop organization, see [Organizing Dashboards](/dashboards/organizing-dashboards.md).
## Where to find dashboards
Dashboards live in the **Dashboards** section of the sidebar. Click the section to expand it and see your existing dashboards. If you haven't created any yet, the sidebar shows **"No dashboards yet"** under the Dashboards heading.
Two controls appear alongside the Dashboards section when it is expanded:
* **Add dashboard** — A plus icon with the label "Add dashboard". Click it to open the creation dialog.
* **Dashboard settings** — A gear icon with the tooltip "Dashboard settings". This opens the dashboard management modal, covered in [Organizing Dashboards](/dashboards/organizing-dashboards.md).
When the sidebar is collapsed, only the add icon is visible.
## Creating a new dashboard
Click **Add dashboard** in the sidebar to open the dashboard creation dialog.
The dialog title reads **"Add dashboard"** with the subtitle **"Create your personalized dashboard, add the necessary widgets to meet your goals."**
### Fields
* **Icon** — Choose a visual icon for the dashboard. The default icon is a house. The selector is 80 pixels wide and sits to the left of the name field.
* **Name** *(required)* — Enter a name for the dashboard. The placeholder text reads **"My dashboard"**. If you try to save without entering a name, the validation message **"Dashboard name is required"** appears.
* **Folder** — Choose which folder to place the dashboard in. The dropdown shows **"None (top level)"** as the default option, followed by any folders you have already created. This field is only available when creating a new dashboard — it does not appear when editing an existing dashboard's metadata.
* **Description** — An optional multiline text field for notes about the dashboard's purpose. The placeholder reads **"Describe your dashboard, if needed"**.
### Saving
Click **Save** to create the dashboard. The dialog closes and the new dashboard opens automatically, ready for you to [add widgets](/dashboards/adding-widgets.md). Click **Cancel** to close the dialog without creating anything.
### Naming conventions for multi-site deployments
For deployments spanning multiple buildings or regions, a consistent naming scheme makes dashboards easier to find. Consider patterns like:
* `Building A — Temperature Overview`
* `Warehouse 3 — Cold Chain Compliance`
* `DC-East — Server Room Environment`
Combine folder structure with clear names so any team member can locate the right dashboard without guessing.
## Viewing a dashboard
Once created, a dashboard appears in the sidebar under its folder (or at the top level if no folder was selected). Click it to open the dashboard view.
The dashboard header shows the **dashboard name** on the left, a vertical divider, and a non-interactive **Live Data** label with an icon on the right. This label is not a connection-health check or proof of a fresh reading. Check the widget's update time and the device's last-reported time before relying on a value. Unlike the clickable Live Data button on the [overview page](/overview.md), the dashboard label has no click action.
To the far right of the header, an **actions menu** (three-dot icon) provides three options:
* **Share dashboard** — Opens the dashboard access dialog, where you can publish the dashboard as a password-protected link. See [Sharing Dashboards](/dashboards/sharing-dashboards.md).
* **Edit dashboard** — Enters edit mode, where you can add, rearrange, and configure widgets.
* **Delete dashboard** — Opens a confirmation dialog (see below).
## Editing dashboard metadata
To change a dashboard's name, icon, or description after creation:
1. Open the dashboard.
2. Click the actions menu and select **Edit dashboard** to enter edit mode.
3. In edit mode, a small **pencil icon** appears to the left of the action buttons — this replaces the Live Data indicator. Click the pencil icon.
4. The edit dialog opens with the title **"Edit dashboard"**, pre-filled with the current name, icon, and description.
5. Make your changes and click **Save**.
The folder field is not available in the edit dialog. To move a dashboard between folders, use the [dashboard management modal](/dashboards/organizing-dashboards.md).
## Deleting a dashboard
To delete a dashboard:
1. Open the dashboard.
2. Click the actions menu and select **Delete dashboard**.
3. A confirmation dialog appears: **"Are you sure you want to delete {dashboard name} dashboard?"** with the warning **"Once deleted, this action cannot be undone."**
4. Click **Yes, delete** to confirm, or close the dialog to cancel.
Deleting a dashboard removes it and all its widgets permanently.
## Related pages
* [Adding Widgets](/dashboards/adding-widgets.md) — Populate your new dashboard with device data.
* [Organizing Dashboards](/dashboards/organizing-dashboards.md) — Create folders and reorder dashboards.
* [Overview Page](/overview.md) — The default summary view that exists before you create any dashboards.
## Associate a dashboard with an application
In the add or edit dialog, choose **Application** to make the dashboard available from that application’s **Dashboard** tab. **Default** keeps it standalone. Save the dialog, then verify the result in [Using Application Dashboards](/applications/using-application-dashboards.md). Layout and widget changes remain in the dashboard editor.
---
# 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/creating-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.
