> For the complete documentation index, see [llms.txt](https://docs.avonnicomponents.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.avonnicomponents.com/flow/tutorials/components/kanban.md).

# Kanban

Step-by-step Kanban tutorials for screen flows: build a pipeline board with totals, move deals safely, act from a card, and organise a busy board.

The Kanban shows records as cards in columns, one column per value of a picklist such as Stage. These tutorials follow a sales team's opportunity pipeline: the board itself, then moving and acting on deals, then keeping a full board readable.

{% hint style="info" %}
New to the component? Start with [Build an opportunity pipeline board with column totals](https://docs.avonnicomponents.com/flow/tutorials/components/kanban/introduction.md). Every other tutorial starts from that board. Keep the [Kanban reference](https://docs.avonnicomponents.com/flow/flow-components/kanban.md) open for every property.
{% endhint %}

## Build the board

Show the quarter's deals by stage, with the total and the average amount on top of each column.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Build an opportunity pipeline board with column totals</strong></td><td>One column per stage, cards for each deal, and the total and average amount at the top of every column.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FVfHBopHsiJgyIuUhzeav%2Fflow-hub-cover-kanban.png?alt=media">flow-hub-cover-kanban.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/introduction.md">Build an opportunity pipeline board with column totals</a></td></tr></tbody></table>

## Act on deals

Let reps move a deal to the next stage and work on it without leaving the screen.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Move a deal and save it safely</strong></td><td>Drag a deal to another stage, let a validation rule refuse a bad move, and react to every saved one.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FhkoIJMsxNgdruHD0HNJZ%2Fkanban-cover-move-a-deal-and-save-it-safely.png?alt=media">kanban-cover-move-a-deal-and-save-it-safely.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/move-a-deal-and-save-it-safely.md">Move a deal and save it safely</a></td></tr><tr><td><strong>Open a flow from a card action</strong></td><td>Reassign or edit a deal from its card, in a side panel, and add a New Deal button above the board.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FRGK2bHbttTAtLJ14dgWW%2Fkanban-cover-open-a-flow-from-a-card-action.png?alt=media">kanban-cover-open-a-flow-from-a-card-action.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/open-a-flow-from-a-card-action.md">Open a flow from a card action</a></td></tr></tbody></table>

## Organise a busy board

Split the stages into lanes and help each rep find the deals they need.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Group cards into swimlanes with totals</strong></td><td>One lane per lead source inside every stage, with a total per lane.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FOxwil4TGcHgjuGByjFPc%2Fkanban-cover-group-cards-into-swimlanes-with-totals.png?alt=media">kanban-cover-group-cards-into-swimlanes-with-totals.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/group-cards-into-swimlanes-with-totals.md">Group cards into swimlanes with totals</a></td></tr><tr><td><strong>Filter, search and order a board</strong></td><td>Filters, a search bar and your own column order, so a long pipeline stays easy to read.</td><td><a href="https://27923732-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F1FUd4apB9YHgCEMUFbVb%2Fuploads%2FKdxBdx75ilvSYJJ9HkiX%2Fkanban-cover-filter-search-and-order-a-board.png?alt=media">kanban-cover-filter-search-and-order-a-board.png</a></td><td><a href="https://docs.avonnicomponents.com/flow/tutorials/components/kanban/filter-search-and-order-a-board.md">Filter, search and order a board</a></td></tr></tbody></table>


---

# 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.avonnicomponents.com/flow/tutorials/components/kanban.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.
