> 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.md).

# Dashboard Builder

- [Overview](https://docs.akenza.io/dashboard-builder/dashboard-builder.md): The Dashboard Builder turns the data stored in akenza into dashboards, signage screens, and links you can share outside the platform.
- [Dashboard Types](https://docs.akenza.io/dashboard-builder/dashboard-types.md): akenza supports two types of dashboard: classic dashboards and signage screens.
- [Managing Dashboards](https://docs.akenza.io/dashboard-builder/managing-dashboards.md)
- [Dashboards Settings](https://docs.akenza.io/dashboard-builder/managing-dashboards/dashboards-settings.md)
- [Dashboard Groups](https://docs.akenza.io/dashboard-builder/managing-dashboards/dashboard-groups.md)
- [Public Links](https://docs.akenza.io/dashboard-builder/managing-dashboards/public-links.md)
- [Dashboard Templates](https://docs.akenza.io/dashboard-builder/dashboard-templates.md)
- [Components](https://docs.akenza.io/dashboard-builder/components.md)
- [Line & Bar Chart](https://docs.akenza.io/dashboard-builder/components/line-and-bar-chart.md): The chart component plots device data over time as a line chart or a bar chart.
- [Map](https://docs.akenza.io/dashboard-builder/components/map.md)
- [KPI components](https://docs.akenza.io/dashboard-builder/components/kpi-components.md)
- [Trend component](https://docs.akenza.io/dashboard-builder/components/kpi-components/trend-component.md)
- [Performance component](https://docs.akenza.io/dashboard-builder/components/kpi-components/performance-component.md)
- [Gauge component](https://docs.akenza.io/dashboard-builder/components/kpi-components/gauge-component.md)
- [Floorplan component](https://docs.akenza.io/dashboard-builder/components/floorplan-component.md)
- [Status component](https://docs.akenza.io/dashboard-builder/components/status-component.md)
- [Device control components](https://docs.akenza.io/dashboard-builder/components/device-control-components.md)
- [Downlink component](https://docs.akenza.io/dashboard-builder/components/device-control-components/downlink-component.md)
- [Slider component](https://docs.akenza.io/dashboard-builder/components/device-control-components/slider-component.md)
- [Button downlink](https://docs.akenza.io/dashboard-builder/components/device-control-components/button-downlink.md)
- [Input field component](https://docs.akenza.io/dashboard-builder/components/device-control-components/input-field-component.md)
- [Image](https://docs.akenza.io/dashboard-builder/components/image.md): Building Digital Twins with Raster Images and SVGs
- [Embedding dashboards](https://docs.akenza.io/dashboard-builder/embedding-dashboards.md)
- [Signage screens](https://docs.akenza.io/dashboard-builder/signage-screens.md)


---

# 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.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.