> For the complete documentation index, see [llms.txt](https://guides.noloco.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.noloco.io/views/display/charts.md).

# Charts

Learn how to add and configure chart views.

{% embed url="<https://youtu.be/ikkMK8mgn0o>" %}

You can easily add charts to your Noloco apps both on views and on blank pages.

In this video, learn how to:

* Configure the charts display option on views
* Choose the perfect chart type for your data
* Make charts take up the full-width of the screen
* Use blank pages to add charts from different tables
* Filter chart data to only show data that meet certain criteria
* Add visibility rules to control who can

{% hint style="info" %}
If you want to add multiple charts to the same page pulling in data from *different* tables, you'll have to add a [Blank page](/pages/blank-pages.md) (as shown in the video) as opposed to using a view.
{% endhint %}


---

# 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://guides.noloco.io/views/display/charts.md?ask=<question>&goal=<user_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.