Kanban View

Overview

The kanban view displays records as cards arranged into columns. The columns are driven by a single-select field on the table, one column per option. End users can drag cards between columns to change the record's status, if they have edit permission on the field.

Use kanban for anything with stages: support tickets, hiring pipelines, content production, sales opportunities, maintenance requests, applications.

Requirements

A kanban view needs a single-select field on the Airtable table. The Kanban option is disabled in the View type dropdown if no single-select field exists. Add one in Airtable first if you need it.

Configuring a Kanban View

1. 1

   Open the Display tab

   In the portal admin, open the role, expand the table, and switch to the Display tab.

2. 2

   Pick Kanban as the view type

   Set the View type dropdown to Kanban. The configuration fields below change.

3. 3

   Pick the group field

   The Group by dropdown lists every single-select field on the table. Pick the field that represents the stages of your workflow (commonly named "Status", "Stage", or similar).

4. 4

   Pick the card fields

   Check the fields you want shown on each card below the title. See Summary Fields and Record Detail for the full reference.

Column Layout

One column appears for each option on the group field, in the order the options are defined in Airtable. Plus a No status column at the start, holding records that have no value on the group field.

To change column order, reorder the options in Airtable. To add or remove columns, add or remove options.

If the group field is set to required in field permissions, the No status column is hidden when no records sit there, and end users can't drag a card back into it.

Drag-to-Edit

End users can drag a card from one column to another to change the record's status. This works when the end user has Edit permission on the group field (set in field permissions).

If the group field is view-only, the cards display but can't be dragged. The status changes immediately when a drag completes; there's no separate save step.

Card Layout

Every card includes:

1. Title (the record's primary field)
2. Card fields (the additional summary fields you picked)

The group field itself is not duplicated on the card, since the column position already shows it.

Permissions

Kanban respects all the usual permissions:

• A field set to Hidden in field permissions never appears on the card or the detail page.
• The group field must be at least View Only for the kanban to render at all, and Editable for drag-to-edit.
• The user-based record filtering still applies.

Tips

• Keep the status field stable. Adding and removing options reshuffles columns for every user. Decide the stages up front.
• Two or three card fields. Owner, due date, customer name. Anything that helps end users pick the right card.
• Combine with a record filter. A kanban for a specific year, segment, or owner gives focus without losing the workflow shape.

Next Steps

• View Types - Compare the four layouts
• Summary Fields and Record Detail - Pick which fields show on the card
• Field Permissions - Control whether the group field is editable
• Supported Field Types - How single-select fields render