> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/data-consumption/dashboards.md). # Dashboards Dashboards allow you to combine charts together to answer business questions. You can share these reports with your colleagues or externally in your apps or publicly ## What is a dashboard ? A dashboard is a page containing multiple charts (charts can be a table, a bar chart, a funnel, a map, ...). Usually, a dashboard will contain multiple charts related to the same topic, or answering different parts of the same question. A dashboard can be shared internally with your team on Whaly, on externally with your customers or business partners, either: * In a passive way by using a sharing link * In a proactive way by using pushes to share your report in Slack or via Email You can make your dashboards interactive by adding filters on a dashboard. These filter will be available for the users and will filter data in the same way on all your configured tiles. --- # 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.whaly.io/data-consumption/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.