> 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/dashboard-types.md).

# Dashboard Types

akenza supports two types of dashboard: classic dashboards and signage screens.

Currently, two types of dashboard are supported. You pick the type when you create the dashboard, and the choice determines how the layout behaves on screen.

## Classic dashboards

Use *classic dashboards* to build scrollable dashboards, unlimited in height. Components are laid out top to bottom and the viewer scrolls through them, so a classic dashboard suits a detailed view that someone reads on a laptop, tablet, or phone.

## Signage screens

Use *signage screens* if you want to limit your dashboard to the screen size, for example when displaying data on a large screen. Everything has to fit the display at once, because nobody is there to scroll: the dashboard is meant to be read from across the room, in an office, a lobby, or a plant.

{% hint style="info" %}
Signage screens are billed separately from classic dashboards. A plan includes an allowance of dashboards and, on the higher tiers, a separate allowance of signage screens, so a plan that covers your dashboards does not necessarily include one. See [akenza.io/pricing](https://akenza.io/pricing) for the current allowances and [Billing & Subscription](/device-management/managing-an-organization/subscription.md) for the plan your organization is on.
{% endhint %}

{% content-ref url="/pages/LUio6GXB830yuxjGB8Oz" %}
[Signage screens](/dashboard-builder/signage-screens.md)
{% endcontent-ref %}

## Choosing between them

<table><thead><tr><th width="220"></th><th>Classic dashboard</th><th>Signage screen</th></tr></thead><tbody><tr><td><strong>Height</strong></td><td>Unlimited, scrollable</td><td>Fixed to the screen</td></tr><tr><td><strong>Read by</strong></td><td>A person at a computer or on a phone</td><td>Anyone passing a wall-mounted display</td></tr><tr><td><strong>Typical use</strong></td><td>Analysis, troubleshooting, detailed monitoring</td><td>A handful of headline figures kept permanently on show</td></tr></tbody></table>

{% hint style="info" %}
Both types are built from the same [components](/dashboard-builder/components.md) and can be shared outside akenza with a [public link](/dashboard-builder/managing-dashboards/public-links.md).
{% endhint %}


---

# 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/dashboard-builder/dashboard-types.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.