> 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 tabs to organize related sections on a page.

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** where you want it on the page.
{% endstep %}

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

Use the **+** in the tab bar to add a new tab.\
Give each tab a descriptive name.
{% endstep %}

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

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

## **Configure the Tabs component**

The tab component consists of two main elements: the **Tabs** and the associated **Containers**.

### Configure the Tabs

A **Tab** is a labeled button that opens its related container.

In **On the form**, configure these basic options:

* **Label** sets the component title.
* **Internal name** is filled automatically. Change it only when needed. Use the **Internal name** in scripts, not the **Label**.

Under **Display**, configure the component appearance:

* **Variant** sets the tabs to **Pills** or **Underlined**.
* **Tabs** lets you rename or delete tabs.
* **+ Add tab** adds another tab.

Under **Behavior**, configure tab-change actions:

* **On change** runs logic when the active tab changes.

### Configure a tab Container

Each **Tab** contains a separate [Container component](https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/create-and-customize-pages/container-component.md)  that you can configure independently. The tab **Container** holds a group of elements.

In **On the form**, configure these basic options:

* **Label** names the tab container.
* **Internal name** is required and identifies the container in logic.

Under **Display**, configure the container layout:

* **Flow** controls how components are arranged.
* **Padding**, **Margin**, **Border**, **Border radius**, **Background**, and **Shadow** control its appearance.
* **Gap** sets the space between components. **Overflow** controls how content behaves outside the container.

Under **Visibility**, choose how the component is shown on the page:

* **Visible**: shows the component on the page.
* **Hidden**: hides the component on the page.
* **Conditional**: defines a **Visibility condition** that controls when the component is shown or hidden.

  Use **Conditional** when the component should appear only in specific cases.

  Build the condition based on user roles, **Tables**, or **Fields**.&#x20;

This only affects what is shown on the page. It does not change records or permissions.

Under **Automations**, control your workflow with:

* **Before show** to run logic before the tab is shown.
* **After hide** to run logic after the tab is hidden.

{% 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ninox.com/builder-hub/visualize-and-organize-your-data/create-and-customize-pages/tabs-component.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.
