> 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/group/groups-dashboard.md). # Group's Dashboard

### Accessing the Group Dashboard To access a group's dashboard: 1. Navigate to the **Assets View** from the sidebar. 2. Click on the **name of the group** you want to open. 3. The **Group Dashboard** will load. *** #### Within the dashboard, you can: * **Reset the dashboard layout** to default if needed. * **Add or remove widgets** to customize how data is displayed. (discover the widgets here: * **Copy the dashboard** layout to other groups for consistency. * **Access the full device list** assigned to the group. * **View and manage Rules** linked to devices in the group. * **Monitor Alarms and Events** related to the devices in the group, for real-time operational awareness. *** This centralized dashboard provides a streamlined view for managing, monitoring, and configuring everything related to the selected group. --- # 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/group/groups-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.