Skip to main content
Kanban view displays records as cards and groups them into columns by field value. Use it for task status, sales stages, content workflows, recruiting pipelines, and other stage-based work. Kanban view stacked by Status, with cards showing owner, due date, and priority

Use Cases

For practical use cases, see AI project management workflows.

Create a Kanban View

1

Create a view

Click + next to the view tabs.
2

Choose Kanban view

Select Kanban view from the view types.
3

Choose a stacking field

Choose the field used to create stacks, such as status, stage, owner, or date.

Stack Settings

Kanban view can stack records by most fields. Attachment and Button fields are not available as stacking fields.

Manage Stacks

When the stacking field is a Single Select field, you can manage options directly from the board:
  • Click Add stack to create a new option.
  • Choose Rename stack from the stack menu to rename an option.
  • Choose Delete stack from the stack menu to delete an option.
These actions change the options in the corresponding Single Select field. Confirm the impact before changing stacks used by other views or workflows.

Configure Cards

Click Customize cards in the toolbar to control what appears on each card. Customize cards panel with field visibility switches, image setting, and Hide field name Show only fields needed to understand the record status, such as title, owner, due date, priority, and key tags.

Move and Edit Cards

  • Drag a card to change its order or move it to another stack.
  • Click + at the bottom of a stack to open the create-record dialog. Set the stacking field value if you want the new record to appear in that stack.
  • Right-click a card to insert a card above or below, duplicate, expand, or delete it.
  • Click a card, or choose Expand card, to open the record details.

Notes

  • When you drag a card to another stack, Teable updates the value of the stacking field.
  • Create, edit, delete, and drag actions depend on your view, record, and field permissions; cards also cannot be dragged between stacks when the stacking field is computed or read-only.
  • For team workflows, consider locking important views so grouping and card settings are not changed by accident.
Last modified on October 21, 2026