> For the complete documentation index, see [llms.txt](https://move-solutions.gitbook.io/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://move-solutions.gitbook.io/untitled/mymove-manual/dashboard.md).
# Dashboard
The **Dashboard** is the landing page of a project. It welcomes you with the **Move Intelligence** bar and shows a set of **widgets** with the status of the monitoring system, the data sources, the team, the alarms of the last two weeks, the map, the repository and the latest reports.
Every widget has a **Go to … →** link in its header that opens the corresponding page, and you choose which widgets to show with **Manage widgets**.
## Manage widgets
By default the dashboard shows four widgets: **System status summary**, **External data sources**, **Team** and **Alarm overview by sensor**. Click **Manage widgets** to personalise it: the panel lists every widget with a switch, so you can add the optional ones (**Map**, **Image**, **Project repository**, **Latest reports**) or remove the ones you do not need.
The choice is saved for the project. Widgets are arranged on a grid; the Alarm overview takes the full width and the optional widgets are added below it.
> ℹ️ When **Map** and **Image** are both active they are shown as a single **Map & Image Viewer** widget, with a selector in the header to switch between the two views.
## Widgets
### **System status summary**
Real-time counters of the **Devices** (total, **Online**, **Offline**, **Unknown**) and of the **Gateways** (total, Online, Offline). **Go to Devices →** opens the Devices page with the full tables.
### **External data sources**
The pipelines that import third-party data into the project, each with vendor, last transmission and status (**Connected** or **Paused**), paginated. **Manage data sources →** opens External data sources. When no integration is connected the widget explains how to import data and links to the same page: pipelines and CSV uploads are always created from there, never from the dashboard.
### **Team**
The members of the project with their initials, name and access role, paginated. **Go to Team →** opens the Team page, where members are added and roles assigned. When the project has no members yet the widget invites you to add them.
### **Alarm overview by sensor**
The alarms of the **last 14 days**, in three blocks:
* **Totals** of **Critical**, **Warning** and **Alert** events in the header, and the table **By sensor type** with the number of devices, the events per severity and the **14-day trend** of each sensor type.
* **Severity by day**: a heatmap with one row per sensor type and one column per day, from today back 14 days, coloured with the highest severity of the day.
* **Last alarm events**: the most recent events across all devices.
**Go to Alarms →** opens the Alarms page. When no device has thresholds yet the widget shows **No thresholds set on any device** and links to Device settings, where thresholds are configured per device.
### **Map**
The devices of the project on the map, with the **Show labels** switch for the device names. **Go to Map Explorer →** opens the Map Explorer. When no device has been positioned yet the widget links to Device visualization.
### Image
The image of the structure (photo, drawing or plan) with the devices placed on it, the same configured in Device visualization. **Go to Device visualization →** opens the page where the image is uploaded and the devices are positioned; when no image has been uploaded yet the widget invites you to **upload an image of your structure**.
### **Project repository**
The number of files, the storage used and the latest files uploaded with format, size and date. **Go to Repository →** opens the Repository.
### **Latest reports**
The latest reports generated in the project, with their download. **Go to Reports →** opens the Reports page; when no report exists yet, **Create your first report** takes you to the template gallery.
####
---
# 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://move-solutions.gitbook.io/untitled/mymove-manual/dashboard.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.
