> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-5.6/getting-started/faqs/vizpads-faqs.md).

# Vizpads FAQs

Find answers to common Vizpads questions in Tellius—learn about chart limits, row-level security, multi-Business View support, and interactive features.

#### **What is the limit on the number of charts I can add to a vizpad and within one tab?**

A Vizpad can have 10 tabs, and each tab can have upto 25 charts.

#### **Does the row-level data security apply to Search and Vizpads?**

Yes, it does. However, it needs to be set up by the admin. Row-level policy is defined for a group over a Business View so that when users search and run analysis on datasets, they only see the data associated with them (and not the data that is private to a different user).

#### **Can selection on one chart act as a filter on another?**

Yes, it can be done by selecting **Keep** or **Drill-in** after clicking on a slice of a chart.

#### **The calculated columns that are displayed during data preparation does not show up when I’m editing a Vizpad. How do I make them visible?**

Go to the required **Business View** and select **Edit**. Add all columns or check the columns you need to pick.

#### **Is there a way to rename the tabs?**

Yes, click on the dropdown in a tab and select **Rename**.

#### **Can I build a Vizpad using multiple Business Views?**

Yes, check out our [multi-Business View Vizpads](https://help.tellius.com/vizpads-explore/creating-vizpads#multi-business-view-vizpads).

#### **Can I develop my own custom visualizations via rest-based APIs?**

Tellius offers two forms of embedding:

* Embedding Tellius modules (UI) into external applications (via Embedding URLs)
* External applications querying and getting results/output via APIs


---

# 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://help.tellius.com/tellius-5.6/getting-started/faqs/vizpads-faqs.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.