> For the complete documentation index, see [llms.txt](https://docs.pentaho.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pentaho.com/pba/pentaho-analyzer-cp/creating-analyzer-reports/visualizations-for-analyzer.md). # Visualizations for Analyzer After you have created an analysis report, you will most likely want to make the report more visually pleasing and meaningful for your audience. Analyzer has quite a few built-in visualizations that give you an effective means for presenting your data in a way that people can intuitively understand. We also give you many different ways to customize your visualizations. Both the **Layout** and **Property** panels in the Analyzer workspace dynamically change based on the visualization that you currently have selected. The **Layout** panel shows you what data is needed for that particular visualization, and the **Property** panel lets you add or change options such as data labels, color patterns, or bullet styles. The optional properties for each visualization type are listed in each section. You can use any or all of these properties for each visualization to make your report more intuitive for your audience. The [Chart Options](/pba/pentaho-analyzer-cp/creating-analyzer-reports/chart-options-for-analyzer-reports-cp.md) dialog box contains more ways to customize your reports. --- # 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.pentaho.com/pba/pentaho-analyzer-cp/creating-analyzer-reports/visualizations-for-analyzer.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.