> For the complete documentation index, see [llms.txt](https://docs.efento.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.efento.io/efento-cloud/advanced/custom-dashboards.md).

# Custom dashboards

The "Monitoring Zone" module in the Efento Cloud platform allows for the flexible design of personalized dashboards. This solution enables the simultaneous observation of key measurement data, device statuses, and active alarms from selected locations in a way that is tailored to the specific operational needs of the company.

{% hint style="info" %}
**A maximum of 5 dashboards can be configured for each organization**. Dashboards are **visible to all users**, but only users with **Administrator and Manager** permissions can edit them.
{% endhint %}

<figure><img src="/files/c2C1qVu5E1hZUHc9HSdt" alt=""><figcaption></figcaption></figure>

### First launch and initialization

Upon entering the module for the first time (indicated by the four squares/tiles icon in the main menu), the system displays a welcoming configuration screen with the message *"Monitor as you need"*.

To start working with the module, click the central "Add first dashboard" button.

### Choosing the creation mode (templates vs. project from scratch)

After clicking the add button, the system will open a dashboard creation dialog box offering five options:

* **Create dashboard from scratch**: A blank workspace where the user independently defines the layout and type of all tiles.
* **Monitor a large organization**: A template optimized for accounts with more than 20 loggers. It utilizes ready-made *Location Status* and *Alarms* tiles.
* **Learn when to react**: A template focused on diagnosing errors and critical situations. It aggregates tiles that inform about alarm states and incidents.
* **Monitor a large organization with maps**: A layout designed for distributed infrastructure (over 20 loggers), combining *Location Status* with an interactive *Object Map*.
* **Overall organization overview**: Dedicated to smaller infrastructures (up to 20 devices). It automatically deploys *Location Status* tiles and a direct preview of the current *Measurement*.

<figure><img src="/files/2z3Cad04yZOMk3X0GrAs" alt=""><figcaption></figcaption></figure>

### Dashboard parameterization and permissions

After selecting a template or a project from scratch, the user proceeds to the metadata configuration window:

* **Select location**: Select the physical location from the drop-down list from which data will be presented on this dashboard.

{% hint style="info" %}
**Note**: The dashboard will filter and display data (alarms, loggers, statuses, maps) *exclusively* from the location selected here.
{% endhint %}

* **Dashboard name**: Enter a unique identification name (e.g., "Cold Rooms – Main").
* **Who can edit this dashboard**: The system informs about the default access rights. Permissions to modify the tile layout and settings are held exclusively by the following roles: Owner, Administrator, and Manager.

Once the fields are filled out, the "**Add dashboard >"** button in the lower right corner will become active.

### Configuration and adding widgets

After creating a blank project or while editing an existing dashboard (via the "Edit dashboard" button in the upper right corner), the user clicks the "**Add widget**" button. The system displays a component selection window:

* **Measurement**: Displays the current, numerical value from the selected logger (e.g., current temperature). When configuring this tile, the user can select which specific logger it should apply to.
* **Line chart (data from the last 24 hours)**: Presents the historical progression of parameter changes from the logger in the form of a time chart from the last 24 hours. When configuring this tile, the user can select which logger it should apply to. If the logger has more than one channel, it is possible to select which channels should be presented on the chart.
* **Location status**: Generates a donut chart summarizing the health of the devices (the number of devices operating correctly, lost, in an alarm state, or without a valid license). When configuring this tile, the user can choose which location it should apply to and which statuses should be visible on the chart.
* **Alarms**: Displays a tabular list of threshold breach events and failures in real time. When configuring this tile, the user can choose whether to present active or inactive alarms. If inactive alarms are selected, it is additionally possible to choose the time range (last 24 hours, last 7 days, last 30 days).
* **Text**: Allows the user to add a custom header, subtitle, or instructions for personnel. It is used to organize the dashboard into logical sections.
* **Map**: Embeds a map / room blueprint with sensor markers superimposed, making it easier to locate devices in the field. When configuring this tile, the user can specify the content of the markers (name, serial number, status, measurement value).

<figure><img src="/files/GwvjsNecmg5mObzHXC1W" alt=""><figcaption></figcaption></figure>

### Working with a ready dashboard

A fully configured monitoring zone allows for multitasking and quick situation assessment:

#### Navigation between dashboards (tabs)

At the top of the screen, the system generates a convenient tab system. The user can instantly switch between different dashboards. A new tab can be added at any time using the "**+**" button.

<figure><img src="/files/fZtLjbrbooEsDHgpO2n2" alt=""><figcaption></figcaption></figure>

#### Control tools

In the upper right corner of the active dashboard, quick management buttons are available:

* **Refresh**: Forces an immediate download of the latest data packets from the server. Dashboards automatically refresh every 10 minutes.
* **Edit dashboard**: Launches the reconfiguration mode, allowing the user to change the position of tiles, delete them, or add new widgets. Additionally, it is possible to rename or delete the dashboard.

<figure><img src="/files/9Rb6qP6HLqHYT8vgE3JK" alt=""><figcaption></figcaption></figure>

#### Editing tiles

Tile editing is accessible after entering the dashboard editing mode. Once editing is complete, the changes must be saved by clicking the "**Save**" button or discarded by clicking "**Discard changes**". The following functions are available in the editing mode:

* **Moving tiles** – Press and hold the four-arrows icon to change the position of a tile. Tiles can be moved freely. When a tile is moved, the remaining tiles will adjust their positions automatically.<br>

  <figure><img src="/files/4bcRhKb4RY5fqOrROgXX" alt="" width="375"><figcaption></figcaption></figure>
* **Resizing a tile** – Press and hold the arrow on the side / bottom right corner of a tile to increase or decrease its size.<br>

  <figure><img src="/files/CTDPDGDD82GnNiIJJItR" alt=""><figcaption></figcaption></figure>
* **Editing a tile** – Changes the parameters of the selected tile; the scope of editing depends on its type. To enter the tile editing mode, select the three dots in its upper right corner and then choose "**Edit**".
* **Duplicating a tile** – Duplicates the selected tile for subsequent editing. To enter the tile duplication mode, select the three dots in its upper right corner and then choose "**Duplicate**".
* **Deleting a tile** – Removes the selected tile from the dashboard. To delete a tile, select the three dots in its upper right corner and then choose "**Delete**".

<figure><img src="/files/rVFb4uMGf4pCwSffBisR" alt="" width="375"><figcaption></figcaption></figure>


---

# 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.efento.io/efento-cloud/advanced/custom-dashboards.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.
