> For the complete documentation index, see [llms.txt](https://kuadron.gitbook.io/reportql/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kuadron.gitbook.io/reportql/report/create-dashboard/dashboard-components.md).

# Dashboard Components

Dashboard components are the building blocks that display your data in an accessible and interactive manner. Common components include:

### Data Tables

**Grid Serverside**

Displays data stored on the server in table format. This component pulls data from large databases or server-based data sources and presents it to the user. This component works server side. This means that for all the operations you do (such as paging, filtering, sorting), it automatically prepares the relevant queries and runs them on the server and returns the results. For this reason, it is suitable for big data.

* **Features**: Paging, Sorting, Filtering, Column Chooser, Excel Export
* **Allow Define Reports:** If enabled, users can create their own reports using this datatable.

*This component does not support complex queries (cursor, union etc).*

<figure><img src="/files/AQ4ANi9vB5saYdbVwH0F" alt=""><figcaption></figcaption></figure>

**Grid Clientside**

Displays data stored on the client-side in table format. Typically used for small and local datasets. This component works client side. This means that it pulls all the data from the query result to the client side and performs the subsequent operations (such as filtering, sorting) through the client. This component can be used for more complex queries (cursor, union etc.)

* **Features**: Paging, Sorting, Filtering, Column Chooser, Grouping, Chart, Excel Export
* **Chart**: If it's enabled, users can create charts with this component.

<figure><img src="/files/RuleJKqIG2No80K9yqjU" alt=""><figcaption></figcaption></figure>

**Pivot Table**

Presents data in pivot table format. This component facilitates dynamic grouping, summarization, and analysis of data.

* **Working Location**: Client-side

**Content Box**

Used to display free-form content such as text, images, or HTML content. Ideal for providing information or explanations to the user.

### Charts

*You need to run the query once to fill the following fields in all chart components.*

<figure><img src="/files/ocp3lcuL5WeJjWe1EYon" alt=""><figcaption></figcaption></figure>

**Pie Chart**

Visualizes data in the form of a pie chart. It displays the proportions of data slices visually.

**Donut Chart**

Similar to a pie chart but with a hole in the middle, showing data percentages.

**Polar Area Chart**

Displays data in a polar coordinate system in area chart format. Used to visually compare different data groups.

**Line Chart**

Displays data in the form of a line chart. Used for visualizing time series or continuous data.

**Vertical Bar Chart**

Visualizes data as vertical bars. Used to compare data across different categories.

**Horizontal Bar Chart**

Visualizes data as horizontal bars. It is the horizontal version of the vertical bar chart and is used for comparing categories.


---

# 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://kuadron.gitbook.io/reportql/report/create-dashboard/dashboard-components.md?ask=<question>&goal=<endgoal>
```

`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.
