> For the complete documentation index, see [llms.txt](https://docs.ninox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/create-and-customize-pages/tabs-component.md).

# Tabs component

Use the **Tabs** component to keep related sections on one page. Use tabs when sections have equal importance. Users can view one section at a time.

## **Add the Tabs component to a page**

{% stepper %}
{% step %}
**Open the Add tab**

In the **Settings** panel, open **Add**.
{% endstep %}

{% step %}
**Add Tabs**

Under **Layouts**, drag **Tabs** to the preferred location on the page.
{% endstep %}

{% step %}
**Create the tab sections**

Use the **+** in the tab bar to add a new tab.\
Rename each tab so users know what it contains.
{% endstep %}

{% step %}
**Add content to each tab**

Drag views, charts, text, or buttons into the active tab **Container**.\
Move and resize each component as needed.\
To adjust tab options in the **Settings**, click an empty area of the container or its border.\
The border appears when you hover over the container.
{% endstep %}
{% endstepper %}

## **Configure the Tabs component**

In **Settings**, review these basic options first:

* **Label** for the title shown on the component
* **Internal name** is filled automatically. Change it only if needed and carefully. When you script, you use **Internal name**, not **Label**.

Use **Display**:

* **Variant** to choose **Pills** or **Underlined**

Use **Behavior**:

* **On change** to run logic when the active tab changes

{% hint style="info" %}
To remove a component from a page, select the component, then click <i class="fa-trash-can">:trash-can:</i> **Delete component** in the blue menu above it.
{% 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 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.ninox.com/builder-hub/visualize-and-organize-your-data/create-and-customize-pages/tabs-component.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.