Views

A collection can have several views — different ways of looking at the same records. Open a collection's Views tab, click Add View, give it a name, and pick a type. People switch between views from the app's toolbar; you choose which one opens by default from the dropdown above the view list.

View types

• Card — a grid of compact cards, each showing a title, an optional subtitle, a status badge (from an enum field), and an optional image slot. Good for catalogs and lists people scan visually.
• Image Card — a full-bleed image card variant of the above.
• Table — a sortable data grid. Pick which fields show as columns, a default sort, and turn pagination on or off.
• Detail — the single-record page, organized into labeled sections (e.g. "About," "Pricing," "Actions") so a busy record stays readable. Every collection gets one by default.
• Calendar — records plotted on a month/week/day calendar, mapped from a date field (and optionally a start/end time and an end date for multi-day events).
• Chart — bar, line, pie, or doughnut charts built from your fields, with a label field and an optional value field (counts records if you leave it blank).
• Dashboard — a grid of panels: either an embedded view or a stat panel (count, sum, average, min, or max over a field) — for an at-a-glance overview of a collection.
• Questionnaire — a step-by-step, one-question-at-a-time form for surveys, interviews, intake forms, and checklists. See Questionnaire views below.

Questionnaire views

A questionnaire turns data entry into a wizard: people answer a few questions at a time, move forward with Next, and Submit once at the end. It suits anything long that's easier to fill in step by step — a patient intake, a site inspection, a customer survey.

• Each section is one step. Add fields to sections in the view editor exactly as you would for a detail view; each section becomes a step, and its label becomes the step's title.
• A field's description is the question. Each field is shown with its description as the heading — falling back to its label if it has no description — so write the full question ("What was the main cause of death?") as the description and keep the label short.
• Validation runs per step. Required fields and Valid if rules are checked before someone can move on, and again on submit — the same rules a normal create or edit form applies.
• The list of answers. Opening the view shows the questionnaires already submitted, as cards. Choose which fields appear on those cards separately from the steps. Tap one to reopen and edit it, or use the + button to start a new one.
• Any field type works inside a questionnaire, including multi-select enums and multi-references.

Filtering

Card, table, calendar, and chart views can expose a filter bar over a chosen set of fields — click Add filter and pick which ones. Text, number, date, boolean, enum, and reference fields all get an appropriate filter control automatically.

Restricting what a view shows

Two independent, optional formulas:

• Show view tab only if — hides the entire view/tab (not just a field), useful for showing a view only to a certain role.
• Filter records — hides individual records that don't match, rather than the whole view.

Sorting

Table, card and image card views have a Sort setting: pick a field and Asc or Desc, and the records are listed in that order (for example newest first by a date field). Sorting uses the value stored in the field, so dates and numbers sort as you'd expect and text sorts alphabetically. A reference field sorts by its stored id rather than the name it displays, so sort by a field on the record itself when you can.

Sections (Detail views)

Detail views are organized into sections, ordered groups of fields and action buttons. A section can have its own visibility formula, so you can show or hide a whole group at once (e.g. an "Admin notes" section only visible to certain roles).

Card views don't use sections. What a card shows is set by its slots (title, subtitle, status badge and image).

Table columns

For table views, the fields you add (in the Fields tab, reused here) become left-to-right columns in the order you place them; action buttons appear together in a trailing column.

Dashboard panels

Each panel is either:

• View — embeds another (non-dashboard, non-detail) view from the same collection, optionally limited to a number of rows.
• Stat — a single number: a count, sum, average, min, or max over a chosen field.

Panels can be filtered, conditionally shown, sorted, sized (quarter/third/half/full width), and reordered by dragging.