A full-page interface fills the whole canvas with a single content type instead of a map. That's all "full-page" means here — the layout has no map area, so a single component takes the entire viewport. Use it when the user's main task is reading or editing records, not exploring a map.
For interfaces that include a map, use the standard (universal) interface template instead — see What is Builder?.
When to use a full-page interface
Pick full-page when the audience needs:
- A spreadsheet-like view of a dataset.
- A kanban board for work that moves through statuses.
- A focused form for collecting submissions.
- A calendar view of date-bound records.
If the audience needs to pan and zoom a map, you want a universal interface, not a full-page one.
Available page types
Each full-page interface is built around exactly one of these components:
Datatable
A spreadsheet-style view of a dataset. Columns map to the dataset's fields; rows are records. Useful for review workflows, audits, and bulk inspection where the map isn't relevant. Clicking a row opens a detail drawer with the full record.
Kanban
A board view where records are cards and columns map to a status field. Drag cards between columns to update the status (the change writes back to the dataset). Useful for tickets, leads, work orders, or anything that progresses through stages.
Form
A standalone form scoped to a dataset. Best for collecting structured submissions when the form is the primary purpose of the page — embed the URL in onboarding flows, internal portals, or email signatures. For form-builder details, see Forms.
Calendar
A schedule view that places records on a calendar based on a date or date-range field. Includes day, week, and month layouts and a count of events per day. Useful for inspections, deliveries, events, and any date-driven dataset.
Create a full-page interface
In the Builder, add a new interface and pick the Full page template (described as "A full-page view without a map"). The new interface starts empty; choose which page type to render and bind it to a dataset.
You can have multiple full-page interfaces in the same project — each with its own page type and dataset — and switch between them using the interface navigation dropdown.
Settings differences
Full-page interfaces share most settings with universal interfaces (Interface Settings), but a few don't apply because there's no map:
- Tools (location search, measure tool, map export, find my location) — hidden.
- Controls (map scale, zoom, 3D mode, basemap, projection) — hidden.
- Static map (Disable interaction) — hidden, since there's no map to disable.
Sections, themes, branding, sharing, and per-interface permissions all work identically to universal interfaces.
Mobile vs desktop
Each full-page type has its own responsive behaviour:
- Datatable reflows to horizontal scrolling on narrow screens.
- Kanban becomes a single-column scroll on mobile.
- Form fields stack vertically by default and scale down on mobile.
- Calendar drops the week/month grid for a list view on mobile.
Combining with universal interfaces
A common pattern is to mix full-page and universal interfaces inside the same project:
- A universal interface for map exploration.
- A datatable interface for the underlying records.
- A kanban interface for status tracking.
Switch between them with the interface navigation dropdown — see Multiple interfaces in a project.