There’s a moment everyone who runs a business on software knows: the data you need is in the table, but the table won’t show it to you the way you think about it. You want deals grouped by stage; it gives you rows by date. You want four columns; it gives you fourteen. So you export to a spreadsheet, and now there are two truths.
Today’s release is aimed at that moment. Every saved view in ONE — and the tasks table — now carries a full toolbar: filter, sort, group, show and hide fields, and save.
The toolbar you already know
We didn’t invent a new interaction language, on purpose. If you’ve used Notion — and statistically, you have — the toolbar reads instantly: chips for filters, a sort control, a group-by, a field-visibility list. The learning curve is “oh, it’s that.”
What’s underneath is one shared library — a single view-configuration model that every table reads and writes. That’s an engineering detail with a user-facing consequence: the toolbar behaves identically everywhere it appears. Learn it on the tasks table and you’ve learned it on every saved view. No surface has its own dialect.
Save means save
Arrange a view — filter to your open deals, group by stage, hide the columns you never read, sort by close date — and save it. That arrangement is the view now. Open it tomorrow, next week, on another machine: same shape.
This sounds small. It’s the difference between a table you configure every single morning (until you stop bothering) and a table that’s already the answer when you open it. The report you’ll actually look at is the one you don’t have to rebuild.
Views are for operating, not admiring
The tables this landed on are the ones you run a business from — tasks, deals, contacts, content. The configurations that matter are operational:
- Tasks grouped by assignee, sorted by due — the Monday view.
- Deals filtered to this quarter, grouped by stage — the pipeline review.
- Contacts filtered to a segment, four columns only — the call list.
Each of those used to be a request to whoever “does reports.” Now each is forty seconds with a toolbar, saved once, opened forever.
One model, everywhere next
Because the configuration lives in one shared library rather than inside any single table’s code, everything that renders rows can inherit it — today’s release covers saved views and tasks, and the same model is what future tables pick up on arrival.
That’s the quiet part of the release: not a feature bolted onto one screen, but a convention the whole product now shares. Your way of looking at the data, remembered — wherever the data shows up.