Skip to content

Saved views

A Saved View captures the current filter selections, search text, visible columns, and column widths. One click switches between views — useful when you wear multiple hats or hand the same project to different colleagues.

Saved views live at the top of the Documents view, next to the Create new view button. The dropdown shows every view you've saved.

When saved views help

Saved views earn their place when you're switching between contexts more than once a day:

  • A reviewer who handles two vendor groups can save one view per group, with vendor-name filters pre-applied.
  • An accountant who runs end-of-month reconciliation can save a view for "Approved this month, not yet exported."
  • A team lead can save a view for "Pending more than two days" to spot stalled documents.

If you only ever look at My tasks with the default columns, you don't need saved views. The product works fine without them.

Creating a view

  1. Set up the Documents view exactly how you want it: pick the status filters, build any custom filter rules, choose visible columns, resize columns if you need to.
  2. Click Create new view (the + button next to the view dropdown).
  3. Name the view.
  4. Save.

The view appears in the dropdown alongside Default. Switching to it restores the saved filter, search, and column state.

What a saved view captures

Every saved view stores:

  • Filter selections — the approval-status strip checkboxes, the All tasks / My tasks toggle, any custom filter rules.
  • Search text — whatever was in the search box.
  • Visible columns — which columns you'd ticked in Manage Columns.
  • Column widths — manual resizes persist.

What's not captured: the documents themselves (the view stores the configuration, not a snapshot of rows).

Editing or deleting a view

Open the view, change whatever you want — filters, columns, search — and save. The view updates with the new configuration.

To delete, open the view and use the delete affordance in the view's controls (TBD on exact UI; behavior is straightforward).

Sharing with colleagues

Saved views can be shared with other members of the project. Each recipient gets their own independent copy — not a live-shared link.

The implication matters: if you tweak your view after sharing, your colleagues' copies don't change. To distribute an update, share again.

Sharing is "fork", not "subscribe"

Saved views aren't a real-time-shared dashboard. They're a way to hand someone the configuration you found useful. After that, your view and theirs evolve independently.

My tasks is not a saved view

The My tasks scope toggle in the toolbar is a separate built-in filter. It works for every user with no setup, and you don't need to save anything to use it. Saved views can include or exclude My tasks scoping, but My tasks itself isn't something you "create" — it's always there.

What's next