Collaboration
The arrangement you keep rebuilding
You filtered, sorted three ways, hid four columns and widened two. A preset saves that whole arrangement — and shares it, so the answer to "how are you looking at this?" is a name instead of a screenshot.
Every morning you open the same view, filter to your region, sort by due date then by amount, hide the six columns you never read, widen the one you always do. Then you close it.
A preset is that arrangement given a name. Not the data — the way of looking at the data.
What is actually in one
Three things, and the third is the one people don't expect:
Filters. The full condition set, not a single expression.
Sorts, multi-level. Due date, then amount, then name. Stored by column UUID rather than by position, which is a small decision with a long tail: reorder your columns tomorrow and the sort still means what you meant. A preset that referenced "sort by column 3" would quietly start sorting by something else the first time somebody dragged a header.
Column overrides, keyed by column UUID: a different display name, a different position, hidden or not, a specific width. This is the part that turns a preset from a saved search into a saved layout. The same view can be a dense twelve-column audit sheet for you and a three-column summary for someone who only needs to know what is overdue — same data, same view, same table, two arrangements.
Two visibility levels
Private is yours alone. Shared means anyone who can see the view can see the preset — and that includes anyone holding a guest share link, not only workspace members. There is no middle setting that admits colleagues but excludes guests, so if a preset's name or its filter values would tell a guest something you would rather they not know, keep it private.
The small conveniences
- A personal default. Pin one and it applies whenever you open the view. Defaults are per-user, so pinning yours does not touch anyone else's.
- Favourites, for the handful you use daily.
- Tags, up to fifty characters each, with tag filtering in the load panel. This starts to matter around the twentieth preset, which arrives faster than you would think on a shared view.
- Usage counts and last-used timestamps, which is how you find out that the preset three people swore they needed has been applied twice since March.
What it is not
A preset is not a permission boundary. Hiding a column in a preset hides it from the arrangement, not from the person — they can clear the preset, or use the API, and see everything the view exposes. Column-level access is a separate concern with a separate mechanism, and a preset is the wrong tool to reach for if the goal is that somebody cannot see a salary.
It also does not carry conditional row styles, which sit on the view itself and are the same for everybody looking at it. Switching presets changes filters, sorting and layout; it does not change the colours.
What it doesn't do (yet)
- Two visibility levels, not three. As above — there is no workspace-only tier that excludes guest link holders.
- No versioning. Updating a shared preset changes it for everyone immediately, with no history and no way back to what it was this morning.
- Per view, not per workspace. A preset belongs to one view; a filter arrangement you want across five similar views is five presets.
- Names are unique per view, per user. Two people can both have a "Mine", which is usually what you want and occasionally confusing in a shared list.
- No scheduling or notification. A preset is a way of looking, not a trigger. If you want to be told when rows match, that is a webhook or a Zap, not a preset.
Verified 24 Aug 2026: FilterPresetResourceTest, 21 tests, all green 2026-08-24, covering create, load, update, default and favourite handling and visibility. The field list is read from FilterPresetDTO and the two visibility levels from FilterPresetVisibility, which declares PRIVATE and SHARED and nothing else. That styles are not part of a preset was checked against the code rather than the docs, since styleRules is a column on the View entity and the app reads it from the view..