> For the complete documentation index, see [llms.txt](https://docs.tomat.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tomat.ai/product-overview/building-reports/designing-reports.md). # Designing Reports ### I**ntroduction** In Tomat, designing reports is a seamless and intuitive process, closely integrated with data flows. Reports in Tomat are directly linked to data flows on a one-to-one basis, providing a dynamic way to visualize and present the results of your data manipulations. ### **Creating a New Report.** 1. Starting from a data flow. To design a new report, open the data flow you wish to visualize. 2. Switch to the report tab. Within the data flow interface, switch to the 'Report' tab to start designing your report. ### **Adding Blocks to Your Report** **Source and output nodes (Tables).** Incorporate tables from your data flow into the report. These can be either source nodes or output nodes, depending on what part of the data you wish to display. **Chart nodes.** Add chart nodes to represent data insights visually. These charts are directly linked to the data within your flow for accurate and dynamic data visualization. **Adding blocks.** Blocks can be added either through the context menu in the flow or by selecting them on the report page. ### **Customizing the Report Page** **Moving Blocks.** Users can rearrange blocks on the report page, allowing for a customized layout that best fits the report's narrative. **Adding New Blocks.** Enhance your report with various block types: * Table blocks. Add tables that represent either source or output nodes from your data flow. * Chart blocks. Incorporate charts for graphical data representation. * Metric block. Add source or output tables as a source of metrics. Metric always shows only one value - the first row from the first column. The name of the metric is the column name. * Header blocks. Use headers for titles and section breaks, providing structure to your report. * Text blocks. Include free text for annotations, descriptions, or analysis. * Divider blocks. Use dividers to separate different sections of the report for better readability visually. **Navigation Panel.** On the left side, a navigation panel similar to Google Slides is available. This feature lets you quickly navigate and moving different blocks, enhancing the ease of report editing and review. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.tomat.ai/product-overview/building-reports/designing-reports.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.