Search documentation

Search docs pages by title or description

Join the waitlist
Browse documentation

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.

Try it: Drag a card into another lane (or press the arrow on a card to advance it), and change the WIP limit to see lanes flag themselves.
Settings
Pipeline
Qualified2/3
Nordic Supply AB
12,000 · Maria
Enterprise
Lumen Studio
3,400 · Jonas
SMB
Negotiation3/3
Beck & Söhne
8,900 · Priya
Enterprise
Harbor Foods
2,150 · Maria
SMB
Vega Clinic
5,600 · Tom
Mid-market
Won1/3
Atlas Logistics
21,000 · Priya
Enterprise
Example. A kanban block over a Deals table with Stage as the lane field and a WIP limit of 3: a lane holding more cards than the limit turns red. Each card shows Company, Value with Owner, and the Segment field as a badge. Dropping a card writes the new stage to the row.

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

SettingWhat it does
Lane fieldThe single-select field whose options become the lanes. Required. Rows holding none of the options gather in a trailing "No value" lane, which a board drops when the lane field itself is required.
Title fieldThe card's headline.
Subtitle fieldOptional second line on each card.
Badge fieldOptional field rendered as a badge on the card.
SortOrder of cards inside each lane.
WIP limitOptional work-in-progress cap per lane; lanes over the limit are highlighted.
Show empty lanesOn by default. Off leaves only the lanes holding at least one card; a hidden lane reappears while a card is being dragged.
Card clickThe 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.