> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/tutorials/guides/how-to-use-dashboards.md). # How to use Dashboards Struct PIM's highly customizable dashboard plays a key role in users day to day work in the system, allowing users to setup widgets according to their needs and preferences. The Dashboard is the first tab in the navigation bar and serves as your central hub for important information. In this guide, we’ll walk you through the process of customizing your dashboard with widgets to display the data that matters most to you. We will also explore the powerful collaboration capabilities of Shared Dashboards, enabling teams to efficiently work together and stay aligned on key priorities. {% embed url="" %} Dashboards in Struct PIM (duration 5:28) {% endembed %} ### Guides * [How to customize a Dashboard](/tutorials/guides/how-to-use-dashboards/how-to-customize-a-dashboard.md) * [How to use shared Dashboards](/tutorials/guides/how-to-use-dashboards/how-to-use-shared-dashboards.md) --- # 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.struct.com/tutorials/guides/how-to-use-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.