Saved views¶

A view is a search and a set of filters, under a name. Instead of rebuilding "decommissioning switches in Aarhus" every morning, save it once and pick it from the Views menu on that list.

Saving one¶

1. Filter the list however you like — the search box, the filter rail, or both.
2. Open Views in the list's toolbar and choose Save current filters.
3. Name it. Tick Share if the whole tenant should have it.

The menu then shows your views and the shared ones, with who owns each. Picking one applies its search and filters; Clear puts the list back to everything.

If you change the filters after applying a view, the button says edited — what you're looking at is no longer what the view describes. Update writes the current filters back to it (your own views only).

Sharing¶

Views are private until you share them. A shared view is visible to everyone in the tenant, and only its author can rename, redefine or delete it — so a view your team relies on can't be changed underneath them.

Sharing a view does not share data. Applying it re-runs your list request, so you see the rows you already had access to: the same shared view can show a site-scoped engineer fewer devices than it shows an administrator, never more.

Which lists have them¶

Devices, IPs, prefixes, VLANs, racks, sites, locations, circuits, cables, clusters, device types, certificates, tunnels, wireless LANs and power feeds.

A list gets saved views by handing the control its object type and its filter handle — the filters themselves come from the columns the list renders, so there's no per-model filter language to learn or maintain.

Advanced filter expressions¶

The Advanced entry at the top of every filter rail holds one expression per list, edited two ways over the same definition:

• a builder — bordered groups of field · operator · value rows. Rows in a group must all match (And adds one); groups combine with Or, so a or (b and c) reads exactly as it looks. Fields come from the list's own columns, and the value box carries a picker (the chevron on its right) listing the values actually present in the loaded rows — pick one or type freely. The ⓘ next to the dialog title is the operator reference;
• a typed expression in a small grammar, for conditions the builder can't express (mixed and/or with parentheses):

status = active and (site.name ~ cph or tags ~ core)
due_date < 2026-09-01 and assignees is not empty
weight > 100 or description is empty

Managing saved filters¶

Customize → Saved filters lists every view across every list — yours and the ones shared with this tenant — with the list it belongs to, its visibility, and its owner. Edit (rename, description, shared) or delete your own from there; the pencil on a view in any list's dropdown jumps straight to its edit dialog. The dialog edits the whole view: name, description, visibility, the search text, the ticked sidebar selections (remove values you no longer want), and the advanced expression with the full builder. New facet picks still come from the list itself — apply the view, adjust, Update.

A line break also works as and — one condition per line reads naturally and shows up as one builder row each.

The grammar: field op value, joined with and / or (and binds tighter; parentheses override). Fields are dotted paths into the row (status.name, site.name, tags); a path landing on an object compares its name, and one landing on a list matches when any element does. Operators: = != (or is / is not), ~ !~ (contains), < > <= >= (numeric when both sides are numbers, otherwise text — which orders ISO dates correctly), and is [not] empty. String compares are case-insensitive; quote values with spaces.

The expression stacks with the facet rail and the search box, counts toward the header's filter badge, and is captured by saved views — so "core switches in CPH due this month" can be one shared view.