Saved views

A saved view is a named snapshot of how a table is set up: its filters, which columns are shown and in what order, the sort and the page size. Save one and you can come back to it, switch between several, or share it with the rest of the team. Views work the same way on the Accounts, Requests and Contacts tables. On Accounts a view also remembers the customers/accounts level and any active segment; the other two have neither, so they remember the rest. Views are kept per table, so an Accounts view never appears in the Requests menu.

Your layout is not a view

The layout you’re looking at is a working copy. It saves itself as you go, the way it always has, and it’s yours alone — filtering, hiding a column or re-sorting changes it immediately and nothing else touches it. A view is separate. When you open one, its layout becomes your working copy. From then on the two can drift: change a filter and the view still holds what it held before, until you save. This is deliberate. It means:

• Nothing changed for you when views shipped. Your existing layout carried over untouched, and if you never open the Views menu you’ll never see a difference.
• A teammate editing a shared view can’t pull the rug out from under what you’re in the middle of.
• Closing a view leaves your layout exactly as it is.

While a view is open, the Views button shows its name. An amber dot on the button means your working copy has unsaved changes against the open view.

Saving a view

Set the table up the way you want it, open Views, type a name and click Save. It’s private to you to begin with. The Views button sits next to the search box on each table. With a view already open you’ll also see:

Switching views

Pick any view from the menu and the table changes to match. If your working copy has unsaved changes, Zudo asks first — Save, Discard, or Cancel — rather than quietly overwriting them. On a shared view you can’t edit, Save isn’t offered, since there’s nowhere for the changes to go; cancel and save them as a new view instead.

Linking to a view

Copy link gives an address that opens the view, such as zudo.so/app/accounts?savedView=12. Opening it switches the table to the view the same way picking it from the menu does, including asking first if you have unsaved changes. Anyone who can see the view can use the link, so a team view’s link works for the whole team and a private view’s link only works for you.

Asking the Assistant for a view

You can ask the Assistant for a view of the Accounts table in your own words, such as “my accounts with health under 60 that renew in the next 90 days, biggest MRR first.” It uses the same filters, columns and sorts the table offers, and the review card lists them, along with how many accounts the view shows you today. The filters it writes all have to apply: it can’t write ANY groups yet, so new filters it gives a view that has them replace the groups. Applying it saves the view as yours, private unless you asked for a team view, and Open takes you to it. It can also change a view you’re allowed to change. It can’t delete one, and it only works with Accounts views for now, not Requests.

Sharing and permissions

Anyone can create a view and anyone can share one with the team. Only the view’s creator and organization admins can change or delete a shared view — a teammate can open it and build on it, but they’d save their changes as a view of their own. Private views stay private. Admins can edit what the team shares, but they can’t see anyone else’s private views.

Defaults

Open this by default decides where you land in a fresh browser — a new machine, a cleared cache, an incognito window. If you already have a layout on that browser, it’s kept and the default is left alone. Defaults are per person: setting one on a shared view doesn’t change where anyone else lands.