Views
Views are saved filters and sort settings on a table. Admins define them once; everyone on the team can apply them with one click from the grid, from a flow, or over the public API.
The Default view
Every table has a Default view that shows all records unfiltered and sorted the usual way. You can't rename, edit, or delete it. Switching to Default from any other view reverts the grid to the unfiltered state.
Picking a view
Click the layers icon next to the Filter icon above the grid. The current view's name is shown on the button. Pick any view in the list to replace the grid's current filters and sort with that view's settings.
Saving and managing views (admins only)
Workspace admins see four extra actions in the view picker:
- Save current as new view — prompts for a name, then saves the current filters + sort. Names must be unique within the table.
- Update current view from filters — overwrites the active view with whatever filters and sort you've got right now.
- Set as default for this table / Clear default — see below.
- Delete current view — removes the active view.
Read-Write and Read-Only members see only the view list.
Default view for a table
Admins can mark one saved view as the default for a table. When any
member loads the table with a clean URL (no ?view= parameter), the marked
default is applied automatically. The marked default is shown with a ★ in
the picker.
Only one view per table can be the default — promoting another view clears the previous one. Use Clear default while on the marked view to remove the flag entirely; the table reverts to "all records unfiltered" on fresh page loads.
When a custom default is set, the synthesised "Default" entry in the picker is shown as All records to avoid two rows both reading "Default".
The marked default applies only to the grid UI. The public API
records-query endpoint with no view_id continues to return everything,
unchanged.
Personal "Current User" filters
User-type fields support a special (Current User) option in the filter
picker. Save a view with, say, Assignee = (Current User) and every
member who opens it sees only their own records — the filter resolves to
whoever is logged in, not the person who created the view. Useful for a
shared "My Tasks" view that works for the whole team without duplicating
it per member.
Editing filters while on a saved view
If you change a filter or click a column header to sort while a saved view is active, the grid keeps that view selected but marks it as having unsaved changes. Your change is applied on top of the saved definition; the saved view itself isn't modified until you choose Update current view from filters. To keep the edited result as a separate view, use Save current as new view instead.
URL
A loaded view puts ?view=<id> on the URL. Paste that URL anywhere to
open the table with that view applied. If you've made unsaved edits on
top of the view, those overrides are included in the URL too so reloads
and shared links keep showing the same grid state.
When a table has a marked default, picking All records (id=0) writes
?view=0 to the URL so reloading keeps you on the unfiltered view rather
than re-applying the marked default.
From flows and scripts
Flow builder has a Get Records From View brick in the Data category. Pick a view, give the result a variable name, and the brick fetches the records the view describes. In PHPScript:
$leads = records_query_from_view(42);
foreach ( $leads as $lead ) {
sys_log($lead["title"]);
}
Public API
Views are accessible over the bearer-token public API — you can list a table's views, fetch one, and query records through a view. Creating or editing views is admin-only and session-only in v1. See the Views API reference.