> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/marketing-intelligence/dashboard-builder.md). # Dashboards Dashboards allow you to organize reports into easily digestible pages. To create a new dashboard, make sure “Dashboards” is selected in the primary sidebar, click “New Dashboard”, and then click “From Scratch”. This will land you on an untitled and empty dashboard. To edit the dashboard’s title, click the pen icon next to its name. Now, you’re ready to add a report. Clicking the + button will launch the report builder, and add the report to the dashboard automatically when you are done. If you want to add a report you’ve already built, you can click “Add Existing Report” instead of selecting a report type. You can use a single report in multiple dashboards. Once you’ve added some reports, you may want to rearrange them. To move a report around, drag it by its header and move it to your desired spot. You can also shrink and stretch reports to fit multiple in the same row by clicking on the ellipsis in the top right corner of the report. A row consists of 4 columns. Every added report starts at a 4-column width and can be stretched all the way down to a single column. If you want to delete the dashboard, hover on its name in the sidebar, click on the ellipsis, and click “Delete.” --- # 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.hockeystack.com/marketing-intelligence/dashboard-builder.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.