For the complete documentation index, see llms.txt. This page is also available as Markdown.

View types (List, Grid, Calendar, Board)

This page describes how to change view type amongst List, Grid, and Calendar views.

One page for every list view mode. /screens-and-components/calendar-view and /grid-view redirect here. How-tos such as Board List View stay short and link to this page.

Applies to List (View Items), List (Update Items), and Select Items. Details, forms, content, and native automation screens do not use these view types.

What this is / when to use it

View type
Enum
Use when
Do not use when

List

LIST

Users scan rows, sort, and open details

You need a month of dates at a glance

Grid

GRID

Title image or card layout matters

You need dense ops tables

Calendar

CALENDAR

The job is a date

The database has no usable date property

Board

BOARD

Users move cards across a select/status

You need a spreadsheet of 20 columns

Before you start

  1. The screen is a list-family screen.

  2. For Calendar: a date property exists (date, or created_time / last_edited_time if you only need a read-only calendar).

  3. For Board: a single-select or status property exists for columns.

  4. For Grid gallery: a files/image property exists for the card image.

Build it

  1. Open the list screen.

  2. Open View type (screen settings).

  3. Pick LIST, GRID, CALENDAR, or BOARD.

  4. Set the mode-specific controls in the table below.

  5. Preview phone and desktop. Board and calendar overflow differently on mobile.

  6. Publish.

Every control

Shared

Control
Options
What it does

View type

LIST / GRID / CALENDAR / BOARD

Layout engine.

Filters / sorts

Builder

Working set. Board columns still honor filters.

In-app filters

DYNAMIC / PRE_DEFINED

End-user narrowing on top of the view.

Grouping

Property

Extra grouping on list/grid. On board, the board property is the primary grouping.

Desktop split

On / off

Master-detail: the list/board/calendar stays on one side, details or update fields on the other. See Desktop view.

Grid

Control
Options
What it does

Grid type

CARD / GALLERY

Card is a compact tile with title + a few fields. Gallery emphasizes the image.

Image property

Files / image field

Card cover. Missing files show a placeholder.

Image style / fill

Orientation + fill enums

How the cover crops.

Aspect ratio

Gallery looks best near 4:3 or 1:1. See the troubleshooting note on grid aspect ratio.

Calendar

Control
Options
What it does

Calendar mode

DAY / WEEK / MONTH / AGENDA

Default visible range. Users can usually switch modes in the live app when you enable them.

Date property

Date field

Where the event sits. All-day vs time follows the property.

Title field

Text

What appears on the event chip.

Color / status

Optional select

Chip color.

DAY and WEEK need a date-time property to be useful. MONTH works with date-only. AGENDA is a chronological list of upcoming dated rows.

Board

Control
Options
What it does

Board property

Select or status

One column per option, plus an empty column when the property is blank.

Card title

Text

Card heading.

Card fields

View components

Keep to three or fewer.

Drag to change

On when the property is writable

Dragging writes the select/status. Formula/rollup columns cannot be drop targets.

What users see

  • List. Rows. Tap opens details or reveals update fields.

  • Grid. Cards or gallery tiles. Tap opens the same destination as list.

  • Calendar. A day/week/month/agenda of dated rows. Tap opens the record. Creating from a calendar slot (when enabled) opens the create form with that date prefilled.

  • Board. Columns. Drag updates the board property. Tap opens the record.

Desktop split: selecting a card/row/event loads the details or update pane without leaving the view.

Limits and plans

  • Calendar without a date property falls back to an empty month. It will not invent dates from text.

  • Board columns follow Notion select options. Renaming an option in Notion requires sync before the column title updates.

  • Dragging on a board is a write. Guests on a public app can change Notion data if the screen is visible and the property is writable.

  • Large boards (many options × many cards) are slower on phones. Filter the working set.

  • Grid GALLERY is not a second product. It is a GRID subtype.

Example

A field-ops app has Jobs.

  • Dispatch uses Board on Status (Scheduled / On site / Done). Drag is on.

  • The same database has a second screen This week as Calendar WEEK on Scheduled date.

  • Marketing uses a third screen Portfolio as Grid GALLERY on the cover file.

Three screens, one database, one view-type page.

Fix problems

Symptom
Likely cause
What to do

Calendar empty

Wrong or missing date property

Bind a real date field. Sync.

Board has no columns

Property is not select/status

Change the board property.

Drag does nothing

Property read-only, or disable editing

Check field map.

Gallery has no images

Files property empty or mapped as URL with no preview

Use a files property; sync.

Old Calendar / Grid docs disagree

Those URLs are stubs

This page is canonical.

Next: Filtering, Sorting, or Grouping and In-app Filtering. Desktop split details: Desktop view.

Last updated