> For the complete documentation index, see [llms.txt](https://docs.gridmate.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gridmate.io/product-tour/kanban.md).

# Kanban

Choose a Kanban board configured in the Lightning App Builder, one built on a list view, or one stored as a record.

GridMate Kanban components show Salesforce records as cards across stages.

They differ mainly in **where the board is configured**, so start with the table below.

## Which Kanban should I use?

| Kanban                                                                                         | Use it when you want…                                                                                      | Good to know                                                                                                                                               |
| ---------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [User Kanban Board](https://docs.gridmate.io/product-tour/kanban/user-kanban-board.md)         | To create boards as records, configure them with the Config Wiz and reuse them on any Lightning page.      | Users need both the **GridMate User** and **GridMate Kanban User** permission sets.                                                                        |
| [Kanban Board](https://docs.gridmate.io/product-tour/kanban/kanban-board.md)                   | To track records as cards across stages, with grouping, totals, filters, card ordering and stage controls. | Added to an app page with **GM - Kanban Board** and configured in the Lightning App Builder. The **Stage Field** can be a lookup, for example `AccountId`. |
| [Kanban List View Grid](https://docs.gridmate.io/product-tour/kanban/kanban-list-view-grid.md) | To browse the records of a list view across Kanban-style stages defined with filters.                      | The stages come from the **Kanban Stages** property; the demo uses Open, On Hold and Closed on Case.                                                       |

## Go further

* [Grid - Mass/Record Actions](https://docs.gridmate.io/advanced-guides/grid-actions/actions-library.md): add quick actions and flows to a board.
* [GM - Kanban Board](https://docs.gridmate.io/package-reference/components-library/kanban-and-pivot/gm-kanban-board.md): every property of the Kanban Board component.
* [GM - ListView Kanban](https://docs.gridmate.io/package-reference/components-library/kanban-and-pivot/gm-kanban-data-grid.md): every property of the list view Kanban component.


---

# 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.gridmate.io/product-tour/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.
