> 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/work-with-views/kanban-view.md).
# Kanban view
Group records by status and move them through your workflow.
Use a Kanban view to organize records into columns.
\
Kanban columns are based on a single choice field in the table. If Ninox prompts you to group the view, choose the choice field for the columns. If the table has no choice field, create one first.
In **Kanban view** you can:
* Use **Sort** to control the card order in each column.
* Use [**Filter**](#filter-records-in-a-view) to show only the records relevant to the current workflow.
* Use **Configure cards** to adjust the information shown on the cards.
* Choose a field to add a title to the card.
* Assign a file field for the card thumbnail.
* Choose a color field for the card color.
* Decide which field contents to show or hide on the card.
To use record-based colors, first create a **Color** field in the table. Ninox then applies the stored color to each Kanban card.
You can open records directly from the Kanban board with a click on the card of the record you want to open.
Open a record with a click on the card in a Kanban
---
# 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/work-with-views/kanban-view.md?ask=&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.
