> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/basics/dashboards.md). # Dashboards - [Use dashboards](https://docs.phocassoftware.com/basics/dashboards/use-dashboards.md): Dynamic, interactive, shared dashboards allow your team to monitor performance and collaboratively analyze the latest data changes. - [Create a dashboard](https://docs.phocassoftware.com/basics/dashboards/create-a-dashboard.md): Create dynamic and interactive dashboards to monitor the KPIs relevant to your role in the business. - [Set a dashboard as your homepage](https://docs.phocassoftware.com/basics/dashboards/set-a-dashboard-as-your-homepage.md): Replace your default Phocas homepage with a dashboard that contains the information you want to view immediately. - [Manage dashboards](https://docs.phocassoftware.com/basics/dashboards/manage-dashboards.md): Update your dashboards as your needs change over time and share your dashboards with your team for easier collaboration. --- # 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.phocassoftware.com/basics/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.