The dashboard & workspace
A workspace is the container holding your cases, dashboard, and config; the dashboard is the view onto the active workspace, where a table of every case becomes maps, calendars, and analytics driven by your fields.
This is the Pro chapter, the graduation from running templates one at a time into running an operation. Free users (The Filler) work one template at a time; Lite (The Library) keeps an unlimited template catalog. Pro is where the workspace and its dashboard appear: free and lite accounts see an upgrade preview of this surface, not the full pipeline. New to the model? See core concepts.
The workspace holds everything
A workspace is the container for one body of work: it holds your cases, the dashboard that displays them, and the config that shapes both (mailboxes, columns, filters, visible views, send templates). The sidebar lists your workspaces; the dashboard is always the view onto whichever one is active. Cases are scoped to their workspace, so two workspaces can reuse the same identifier without colliding, and mailboxes, columns, and filters are workspace config, so a change applies to everyone who shares it. Every account gets one workspace free; creating more, and saving workspace settings, are Pro features.
The inbox table
The dashboard opens on the inbox: one row per case, columns drawn from the workspace's templates. Each output that writes case data gets a column (outputs sharing a data key merge), including derived outputs like AI prompts and calculations; only static and binding outputs stay off the table. Field-visibility config decides which columns show. Click a row to open the case detail panel. The list loads a window and fetches more as you scroll or via Load more cases.
Inside a workspace the sidebar shows All Mailboxes above Inbox, Archived, Trash, and any custom mailboxes; filter pills above the table toggle saved expressions and stack with the active mailbox. The toolbar sort control shows an ↑/↓ arrow (click to flip direction) and opens a two-step menu: top level (Newest/Oldest First, Recently/Least Recently Updated, Case ID, Closest/Farthest from Me once location is shared) and Case data... (the workspace's sortable fields, text alphabetical, dates chronological, numbers numeric). Case-data sorts hide value-less cases (an "N hidden" note shows how many); built-in sorts never hide. Column headers stay in sync. Sort persists per workspace per device, defaulting to Newest First. The inbox row carries no quick-action menu: case-level actions live in the detail panel's ⋯ overflow.
Views your fields power
The table is one of four views, toggled by a switcher: Details (the table), Map, Calendar, and Analytics. All four tabs always render (an admin can restrict which a given worker sees); the value type of your fields drives what each view shows across many cases. Address fields plot every case on the Map (full-screen, by location). Date fields feed the Calendar, laying dated activity across days. Number fields drive Analytics, the workspace's charts and totals. Admins can limit which views a given worker sees.
This is also where aggregation lives. A computed output can sum or roll up other fields within the same case (for example, line items into a total), and the number columns it produces flow into Analytics. Fields can reference existing data within the same case to derive new values; they never pull from other cases. For a repeating set of line items inside one case, use a batch field (repeating rows). The full mechanics of how case data is read, edited, and provenance-tracked live in cases & data.
Managing many cases
Workspaces stay durable as volume grows. Select (toolbar) enters selection mode: the button flips to Done, clicking a row toggles its selection instead of opening it, row checkboxes appear, and a select-all toggles every visible case at once. The batch bar then offers Autofill (a batch run with the dropdown template, a Pro feature), Move to... + Move, and Compose Draft (one Gmail draft for all selected). Click Done to exit and clear the selection.
There is no automatic stage engine that moves cases when fields change: mailbox moves are user-driven, via the detail ⋯ menu's Move to mailbox or bulk select in the table. Move finished cases to Archived, or narrow the active list with filters, to keep the working set tight.
Related
- Cases & data
- Mailboxes, stages & filters
- Core concepts
- Track the invoices: see it in action