Board List View

Board List View

Board List View

Turn a List screen into a Board (kanban) so records appear in columns by Status or Select — then drag cards between columns to update Notion.

What changed List screens gain a Board view type alongside List, Grid, and Calendar. Columns come from the screen’s grouping field. When grouping is a Status or single Select field and multi-row update is allowed for that field, makers and end users can drag cards between columns to write the new value back to Notion.

---

What you get

Capability	What makers configure	What end users see
Board view	Appearance → View type → Board	Horizontal columns (one per option)
Grouping	Behaviour → Grouping on Status or Select	Column headers match Notion options
Drag and drop	Grouping field editable + multi-row update allowed	Drag a card to another column updates Notion
Open record	Unchanged on-click / Details link	Tap a card to open Details

Builder Board preview with Status columns

---

Before you start

You need:

• A List (View Items) screen

• A Notion Status or Select property to group by

• Reload Data so options and colors are current

• Permission to Publish

Tip Board works best when every option you care about exists in Notion (including empty columns such as “Not started”). After changing options in Notion, use Reload Data before you publish.

---

Step 1 — Switch the List to Board

1. Open the List screen in the builder.

2. Open Appearance (or the list view type control).

3. Set View type to Board.

4. Confirm the preview switches from a vertical list to columns.

List screen ready before Board configuration

---

Step 2 — Group by Status or Select

1. Open Behaviour → Grouping.

2. Enable grouping and choose the Status or Select field (for example, Status).

3. Set sort order (ASC / DESC) for column order.

4. In preview, confirm columns match your Notion options (for example Not started, Scouting, Open, Closed).

Grouping is required for Board Without grouping, Board has nothing to form columns from. Reference-list components stay List/Grid only — Board is for full List screens.

---

Step 3 — Enable drag-and-drop writes (optional but recommended)

Drag between columns updates the grouping field when:

1. View type is Board

2. Grouping field is Status or single Select

3. Multi-row update is allowed on the List and includes an editable control for that field (or the field is otherwise writable for Board DnD)

Then:

1. In builder preview, drag a card from one column to another.

2. Confirm the card stays in the new column after the update.

3. Publish, open the live app, and repeat the drag on a real device or desktop browser.

Board drag in builder preview

Published Board with restaurant cards

---

Step 4 — Publish and verify Notion

1. Publish the app.

2. Drag a card on the published Board.

3. Open the same page in Notion and confirm Status/Select matches the column you dropped on.

Published Board after drag

---

Checklist

• View type is Board

• Grouping uses Status or Select

• Columns show after Reload Data

• Drag moves the card and updates Notion (when DnD is intended)

• Tap still opens Details

• App is Published

---

Troubleshooting

Symptom	Likely cause	Fix
No columns	Grouping off or wrong field	Enable grouping on Status/Select
Drag does nothing	Field not writable / multi-row update off	Allow multi-row update for that Status/Select; publish again
Save error in builder	Invalid grouping sort value	Use ASC / DESC only
Empty Board	No records or filters hide all rows	Clear filters; confirm data after Reload Data
Reference list has no Board	By design	Use a full List screen

---

Related reading

• Board layouts and Details polish (overview)

• View Types (List, Grid, Calendar) — Board is the new option alongside these

• Filtering, Sorting, or Grouping Items

• 20 Jul 2026 Release

Annotated builder screenshots

Annotated builder screenshot: View Type

Annotated builder screenshot: Appearance

Annotated builder screenshot: Data mapping

Complete Builder Options Reference

Board is an Appearance → View Type on List screens. Full list options: List (View Items) / List (Update Items).

Appearance

View Type = Board

What it does: Renders rows as columns by a select/status property. How to use it: Pick Board, then ensure Title + the board grouping field are mapped. Why / recommended default: Use for status pipelines; keep List for dense scanning.

Data → Title / Tag

What it does: Controls card primary text and optional status chip. How to use it: Title = recognizable name; Tag = status/priority. Why / recommended default: Never leave Title empty on Board.