Case detail sections
The case detail panel has a Summary, Case Data, Files, Activity, Outputs, and Collaborators section. The case header has a three-dots overflow menu with Edit case, Compose share, Generate, Move to mailbox, and Delete case.
Last updated
The case detail panel has a Summary, Case Data, Files, Activity, Outputs, and Collaborators section. The case header carries a three-dots overflow menu with the case-level actions; per-section affordances live inside each section.
What you need
- A case open in the dashboard
The case-header overflow menu
The case header's ⋯ (three-dots) button opens a single menu with every case-level action. The items appear in this order:
- Edit case — switches the panel into edit mode. While editing, a footer at the bottom of the panel exposes Cancel and Save changes.
- Compose share — opens the send composer. The resulting recipients/subject/body/files are turned into a real Gmail draft in your own Gmail mailbox; Gmail's compose view opens in a new tab and you review and click Send from inside Gmail. Requires the Compose Emails capability (Settings → Team) and your Gmail connected at Settings → Integrations. Document Blueprint never sends directly.
- Generate — appears for templates with at least one source tab. Produces the combined PDF onto the case.
- Move to mailbox — a select inside the menu. Pick the destination mailbox (Inbox, Archive, Trash, or any custom mailbox) to move the case.
- Delete case — danger action at the bottom of the menu.
Each item respects role-based capabilities — a member without the right permission doesn't see it.
There's no surfaced "Autofill" button on the case header. Autofill runs from the review modal — see running autofill for the entry points.
The standard sections
Summary
The top section. Shows the identifier, the most-important field values, and quick stats (file count, activity count, last updated).
Case Data
The Case Data section groups every field on the case by provenance so you can see where each value came from at a glance:
- User Input — form-question fields collected from a worker or client. Sticky: extraction never overwrites these.
- Extracted — fields the AI populated from the source files. Extraction metadata (when each file was last extracted, the model used, token cost) lives in a single case-level Extraction Runs panel rather than per row; that panel shows a yellow staleness dot on any file whose template has changed since the last run, with a per-file Re-extract button.
- Computed — fields whose value is derived at read time from an expression over other case fields (e.g. "days outstanding"). Read-only — to change the result, change the inputs it depends on.
Empty fields are hidden — the section only shows what's actually on the case. Extraction metadata (model, run time, token cost) lifts to a single case-level panel rather than repeating on every row.
Editing an Extracted field doesn't move the row to User Input — the row stays in the Extracted bucket but shows an "edited" indicator and a history popover with the diff. Your edit is sticky; the next re-extraction skips that field unless you clear the override.
Static, system, and company-profile fields don't appear in the Case Data section at all — those are workspace-level stamps (company name, today's date, etc.) that resolve at render time and surface only on each generation event in the activity timeline. The case detail panel only shows fields that are case-specific.
Adding a field on the fly
The case-edit grid ends with a dashed + Add field tile. Click it, type a field name like Permit Number and a value, and the field is added to this case. If a field with the same name already exists in the workspace, your value writes to that field — no duplicate is created. Otherwise the field is appended to a workspace-level Custom case fields form template, so it's available for future cases too.
Files
The list of files attached to the case. Click any file tile to preview it inline (mobile opens full-screen); each tile also has a Send action and (with edit access) a Delete action. Files outside your visible categories are hidden.
To upload a new file, open Edit case from the overflow menu — the edit form exposes an Upload File section with a file picker, category selector, and optional description. See uploading files for details.
Activity
The chronological timeline — notes, form submissions, generations, and system events. The composer on this surface is for notes only: free-text body, optional event date, and optional attachments. See the activity timeline for the full breakdown. Form submissions land in the timeline when a client fills a form from the portal — they aren't filled from this composer.
Outputs
Generated PDFs from autofill and Generate runs. Click any output to preview or download.
Collaborators
Two panels:
- Team — workspace members assigned to this case, scoped by visible categories.
- Clients — external people with portal access; each row can expand to manage which form templates they may fill from the portal.