View Types
Pick how each portal table is displayed to end users: table, gallery, kanban, or calendar. Each view has its own configuration.
Overview
Every table in a portal can be displayed in one of four layouts. The right choice depends on the shape of the data and what end users need to do with it. Pick the view per table, in the portal admin.
| View | Best for |
|---|---|
| Table | Tables with many fields, structured data, lists where columns matter |
| Gallery | Anything with a visual hook: properties, products, people, portfolio items |
| Kanban | Workflows with stages: tickets, applications, candidates, content production |
| Calendar | Anything placed on a date: bookings, events, deadlines, schedules. Switch between month and week views. |
Picking a View Type
- 1
Open the table settings
In the portal admin, open the role you want to configure and expand the table you want to change.
- 2
Switch to the Display tab
The table settings panel has two tabs: Access (table and field permissions, record filtering) and Display (view type, field selection, and default sort). Click Display.
- 3
Pick a view type
Use the View type dropdown to pick Table, Gallery, Kanban, or Calendar. The fields below the dropdown change depending on what the view needs.
Requirements per View Type
Each view (other than Table) needs a specific field type to be present on the Airtable table. The dropdown disables options when the required field is missing.
- Gallery: any field type works as the card body. An attachment field is optional, used as the cover image.
- Kanban: requires at least one single-select field to group records into columns.
- Calendar: requires at least one date or dateTime field to place records on the calendar.
- Table: no field requirements.
If you want to use Kanban or Calendar but the table is missing the required field, add it in Airtable first.
What Lives on the Row vs the Detail Page
Every view has the same idea: the row, card, or calendar entry shows a curated summary of the record, and clicking it opens a dedicated detail page with everything else. You choose which fields appear on the summary in the Display tab. See Summary Fields and Record Detail for the full reference.
This matters most on wide tables. A table with 100 columns is unreadable as a row. Pick five or six summary fields, let the rest live on the detail page, and users get a clean list plus the full record one click away.
Per-Role Configuration
View type is configured per role. Different roles in the same portal can see the same table as different layouts, for example a kanban for the ops team and a gallery for clients.
Next Steps
- Summary Fields and Record Detail - Pick which fields show on the row or card
- Gallery View - Cover image and card fields
- Kanban View - Group field and drag-to-edit
- Calendar View - Date field and calendar behaviour
- Field Permissions - Control field-level visibility (a hidden field never shows in any view)