> 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/9.3-analytics/pentaho-analyzer-cp/get-started-with-pentaho-analyzer.md).
# Get started with Pentaho Analyzer
Display and work with data in Analyzer through panels. For example, you can view and work with Steel Wheels data in the Analyzer panels by performing the following steps:
1. From the User Console Home page, click the **Browse Files** button. In the **Browsing** pane, click to expand the **Public** folder, then click to expand the **Steel Wheels** folder.
2. In the center pane, double-click on **European Sales**. The Opened page appears with the Analyzer report. Click the **Add More Fields** and **Rearrange Fields** icons on the toolbar to expand the **Available Fields** and **Layout** panels.
| Item | Name | Function |
| ---- | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| 1 | Opened view | Displays quick access buttons across the top to create and save new Analyzer reports, Interactive Reports, and Dashboards. Opened reports and files show as a series of tabs across the page. |
| 2 | **Available Fields** and **Layout** panels | Use the Available Fields and Layout panels to drag levels and measures into a report.Your report displays changes in the Report Canvas as you drag items onto the Layout panel.
Delete a level or measure from your report by dragging it from the Layout panel toward the lower right corner of the Report Canvas. As you drag it, a trash can icon appears in the lower right corner of the canvas.
|
| 3 | **Report Canvas** | Shows a dynamic view of your report as you work to build it. The look of your report changes constantly as you work with **Available Fields** and **Layout** panels to refine it.The **Report Canvas** shows different fields based on the chart type selected. |
| 4 | **Analyzer Toolbar** and **Filters** | Use the **Analyzer Toolbar** functions to undo or redo actions, hide lists of fields, add or hide filters, disable the auto-refresh function, adjust settings, and change the view of your report.Use the **Filters** panel to display a list of filters applied to the active report, or edit or delete filters. |
---
# 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.pentaho.com/pba/9.3-analytics/pentaho-analyzer-cp/get-started-with-pentaho-analyzer.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.