> 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/kanban-component.md).

# Kanban component

Use a **Kanban** component on a page when records move through clear stages. It works well for tasks, leads, approvals, and support tickets.

Before you add a **Kanban** component, make sure your table has:

* One field that defines the stage or status
* Clear values for each stage
* Optional fields for card details, colors, or thumbnails

{% hint style="info" %}
Use one clear **Single-choice** field, such as Status, to define the columns. This keeps the board easy to understand.
{% endhint %}

## **Add a Kanban component to a page**

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

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

{% step %}
**Add Kanban**

Under **Views**, drag **Kanban** to the preferred location on the page.
{% endstep %}

{% step %}
**Configure the Kanban**

In the component **Settings**:

* Choose the source **Table**.
* Choose the Single-choice field that defines the columns in **Group by field**.
* **Filter** if you want to show only a selection of records.
  {% endstep %}

{% step %}
**Review the result**

Check whether the columns and cards show the records you expect.\
Then drag the component to move it on the page.\
Use the resize handles to adjust its size.
{% endstep %}
{% endstepper %}

## **Kanban component settings**

In **Settings**, you can define the basic component details:

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

Under **Behavior**, configure how the board works on the page:

* **Table** to choose the source table
* **Group by field** to choose the Single-choice field that defines the columns
* <i class="fa-eye">:eye:</i> x **hidden columns** to control which fields Ninox shows on the cards, search for fields, and use **Hide all** or **Show all**
* **Filter** to limit which records users can see with one or more conditions
* **Show empty lane** to show columns even when they contain no records
* **Show search field** to show a search field at the top of the board

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

* **Visible** to show the component on the page
* **Hidden** to hide the component on the page
* **Conditional** to define a **Visibility condition** that controls when the component is shown or hidden

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

  Build the condition based on **Fields** and **Tables**.

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

{% 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/kanban-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.