Kanban block
Data view
The kanban block puts records on a board: one lane per option of a select field, one card per record. Dragging a card to another lane updates the underlying field — the board is the edit surface.
When to use it
- Pipelines with stages: deals, applicants, support tickets, content production.
- Task boards where moving work between states should be one gesture.
- Capacity-sensitive processes — set a WIP limit and overloaded lanes flag themselves.
Settings
| Setting | Options | What it does |
|---|---|---|
| Lane field | select field | The single-select field whose options become the lanes. Required. |
| Title field | — | The card's headline. |
| Subtitle field | — | Optional second line on each card. |
| Badge field | — | Optional field rendered as a badge on the card. |
| Sort | field + asc/desc | Order of cards inside each lane. |
| WIP limit | 1–99 | Optional work-in-progress cap per lane; lanes over the limit are highlighted. |
| Card click | record view | The record page a card opens when clicked. |
Dragging between lanes writes to the lane field, so it honors permissions: viewers whose role can't update that field see a read-only board.
Like every block, this one also has the shared block settings: a title and optional description, a header you can show or hide, auto-height, conditional visibility, and role-based visibility, plus the source table and record-filter settings shared by all data blocks.