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

# Select Home-Dashboard

The Home Dashboard is the primary dashboard that appears on the platform’s homepage, providing an at-a-glance overview of key device metrics and data. It is customizable to display the most relevant widgets, allowing users to prioritize important information. Configured by the tenant administrator, the Home Dashboard ensures a unified view for all users within the tenant

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdbhFiyStdmnNLZUbpcuWpf9rhw_uvL7m79IXFFSTp8Onp426uTGWrGjqaDnqpQf3UEtteM7POlNyZuYmYlO6RwiQJta52QlqtNrRhiOIGG9v-HGep7Eidlreno6sEl8gDG1ZKyiw?key=M-g4csUEzYvWKn331EzU-Woy" alt=""><figcaption><p>home-dashboard</p></figcaption></figure>

## Set Up Home Dashboard

1. Ensure to be with-in the Cockpit menu and click on Dashboard.
2. Select an existing dashboard by its name or description.
3. Click on the ⋮ (ellipse) menu on the selected dashboard card and choose Edit.
4. Check the box labeled Home.
5. Click Save.

This sets the selected dashboard as your personal Home Dashboard. Be sure that the chosen dashboard contains the most relevant data for your team or personal use.

<br>


---

# 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/select-home-dashboard.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.