> For the complete documentation index, see [llms.txt](https://docs.g-iot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.g-iot.io/platform-user-guide-book/dashboards.md). # Dashboards The Dashboard is a central feature of the platform, designed to provide users with a customizable and organized view of their device data and metrics. Dashboards support the visualization of real-time and historical data through various widgets, including charts, tables, and maps. They can be configured to display data for individual devices, groups of devices, or tenant-wide metrics, making them a powerful tool for monitoring, analysis, and decision-making. Dashboards offer flexibility in usage, allowing them to be: * Set as Home Dashboard: Displayed as the main dashboard for all users in the tenant. * Shared Publicly: Made accessible via a public URL for external viewing. * Quick Access Dashboards: Added to the side menu for streamlined navigation to frequently used dashboards. This adaptability ensures critical information is always available in the most convenient and effective format.

--- # 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.g-iot.io/platform-user-guide-book/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.