View Types

Overview

Every table in a portal can be displayed in one of five 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.

Picking a View Type

1. 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. 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. 3

   Pick a view type

   Use the View type dropdown to pick Table, Gallery, Kanban, Calendar, or FAQ. 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.
• FAQ: requires a viewable text field for the question and a different one for the answer. The answer takes single line text, long text, rich text, AI text, and formulas, rollups or lookups resolving to one of those; the question is narrower, taking single line text, long text, and formulas or rollups resolving to one of those, because it is printed as a plain heading.
• Table: no field requirements.

If you want to use Kanban, Calendar or FAQ but the table is missing the required field, add it in Airtable first.

Grouping Rows in the Table View

The table view can group rows under collapsible headers, one per value of a field you pick, the same way Airtable's grid does. Each header shows how many records are in that group, and records with no value collect under a "No value" group at the top.

Set it with the Group by dropdown in the Display tab, which appears when the view type is Table. You can group by a single select, multiple select, checkbox, collaborator, or linked record field. Date, number, and text fields are not offered: they produce too many groups to be useful.

End users see the records under collapsible headers, one per value, each with an exact count.

A few things worth knowing:

• Sorting still applies inside each group. Grouping decides the blocks, sorting orders the rows within them.
• Multi-value cells group by the whole combination. A record tagged "Design, Urgent" sits in its own group rather than appearing under both, so every record is counted exactly once and the group counts always add up.
• Groups can start closed. Tick Start groups collapsed, under the Group by dropdown, and people see the headers and their counts first, then open the groups they want. It is worth turning on when the groups are long, or when most people only care about one of them. Either way anyone can collapse and expand any group as they read.
• Grouping needs the whole table at once. Counting a group means having every matching record, so the portal loads them all rather than one page at a time. Above 500 records it stops and shows the table ungrouped with normal pagination, along with a note explaining why. Nothing is hidden, and filtering the table down brings the grouping back.

To let people choose the grouping themselves rather than fixing it, see Filter and Sort Controls.

The FAQ View

The FAQ view renders a table as an accordion: the question field becomes the heading, and the answer field becomes the panel that opens under it. It is the layout for the tables people read rather than work with, where a table row truncates the long answer to the one line the reader actually wanted.

Set it with the Question field and Answer field dropdowns in the Display tab, which appear when the view type is FAQ. A third setting, Start answers expanded, decides whether the page opens as a list of questions or with every answer already open. Either way a reader can open and close whatever they like, and more than one answer can be open at once.

An FAQ loads the whole table rather than a page at a time, so nothing is one Next button away from being read as unanswered. Like the kanban and calendar views, it stops at 500 records.

See FAQ View for the full reference.

What Lives on the Row vs the Detail Page

The table, gallery, kanban and calendar views share 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. The FAQ view is the exception, and has no summary-field picker: its two fields are the question and the answer. 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
• FAQ View - Question and answer fields, and whether answers start open
• Field Permissions - Control field-level visibility (a hidden field never shows in any view)
• Landing Page - A table's view type sets its card icon on the navigation landing page
• Filter & Sort Controls - Let users filter, search and sort whichever view a table uses
• Related Tabs and Nested Tables - A related tab inherits the child table's view type