Saved Views: Filters That Survive Monday Morning

Every operator has a version of the list they actually need: open inbound for this warehouse, outbound waiting for packing, settlements missing cost allocation, collections for next week. Rebuilding that filter stack every morning is not workflow. It is a tiny ritual of annoyance.

What a saved view stores

A saved view stores the list context: filters, sort, visibility and whether it should be pinned or default. It does not copy the rows. The next time the user opens the view, the database is queried again with the same lens, so the work is current instead of fossilized.

Where it exists

Saved views are available on inventory, inbound, outbound, collections, contracts, settlements, invoices, demanufacturing and components. Companies and contacts stay out until their filter patterns justify it; not every list needs a trophy shelf.

You do not start with an empty bar

Every new tenant lands with a starter set of twenty-one views, seeded once at signup: eight on inventory, two each on inbound, contracts, invoices, demanufacturing and components, and one each on outbound, collections and settlements. They carry a Starter badge and the author label “ReVend starter” in the manage dialog, and they are ordinary views in every other respect — an admin or manager can rename them, delete them or build team versions on top. A fresh team sees on day one what “Grade A — Ready to Sell” or “Awaiting Erasure” means as a filter set, instead of learning the bar by trial and error.

Personal and shared habits

Anyone can keep private views for their own workflow. Shared views and the starter views are visible to the whole team, but only an organization admin or manager (or platform staff during support) can change or delete their definition — a team agreement should not break because someone clicked the wrong pencil. Pinning and choosing a default are personal: two colleagues see the same catalog of views and each decide which ones sit in their bar and which one loads first. A saved view stores its creator’s name. When that name is available, the manage dialog shows it; otherwise it uses a team label. Every change to a view is written to Activity.

Why it matters

Saved views make repeated work predictable. They also reduce mistakes: when the filter is named and reused, operators are less likely to ship the wrong slice of reality because one checkbox reset overnight.