> ## Documentation Index
> Fetch the complete documentation index at: https://docs.helmkit.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Filters & views
> Narrow Triage with the filter menu, sort, group, and horizon controls — and save layouts you return to often as personal views
Triage's filter bar has two halves. The left is about **what you're looking at** — a reset button and your saved views. The right is about **how the list is shaped** — filters, sort, grouping, and how far into the future you're peering.
## The filter bar, left to right
The leftmost button. Click it to reset everything back to your default
state — which for an admin or owner is every signal, no filters, 2-week
horizon. For non-admins, it's the same plus an **Assigned to me**
assignee filter pre-applied. Right-click "Everything" to save your
current state as a new view.
Any saved view you've pinned shows up as a chip next to "Everything."
Click a pinned chip to load the view. Right-click (or use the
context-menu icon) to edit, unpin, or delete it.
If you've loaded a view that isn't pinned, it appears as a chip here
while it's active — and disappears when you click "Everything" or load a
different view.
The bookmark icon next to the chips. Opens a menu listing all your saved
views (pinned and unpinned) with previews, plus pin/edit/delete controls
and a **Save current view…** option at the bottom.
Opens the multi-axis filter menu. See [The filter menu](#the-filter-menu)
below for everything it can do. A small badge on the Filter button shows
how many filters are currently active.
Dropdowns for each. Sort and Group each take a single choice;
Horizon accepts presets (3 days, 1 week, 2 weeks, 1 month, 3 months) or
any custom date via a calendar.
The arrow-icon button at the far right — same behavior as clicking
"Everything."
## The filter menu
Click **Filter** in the filter bar to open this menu. Everything in here stacks — picking multiple filters narrows progressively.
Scope action-item entries by who they're assigned to. Compose freely:
* **No assignee** — unassigned items only
* **Current user** — items assigned to you
* **Each team member** — check one or more teammates
Selections combine with OR — picking "No assignee" and "Célia" shows
both groups together. This filter only narrows action-item entries;
runs, invitations, and integrations pass through regardless.
A checkbox per signal, grouped by what the signal watches:
* **Action items** — Overdue, Unassigned, Assigned to me
* **Runs** — Over capacity, Inconsistent, Missing tickets, No guide assigned
* **Guide invites** — Awaiting guide response, Rejected invitations
* **Integrations** — Sync failures
All signals are checked by default. Uncheck what you don't want to
see. If every signal is on, the filter is considered inactive (no
badge). See the [Signals reference](/features/preflight/triage/signals)
for what each one detects.
Toggle to include entries you've snoozed. When on, snoozed entries
appear with a muted style and a chip showing how long until they
un-snooze. The counter next to the toggle shows how many snoozed
entries you currently have.
Toggle that hides entries whose linked run has already started. Useful
because some signals (like overdue action items) use the item's due
date as their time anchor, not the run date — a ticket that was never
uploaded for yesterday's run still shows up unless this toggle is on.
Narrow to specific booking statuses: Requested, Reserved, Confirmed,
or Cancelled. Useful when you want to focus only on Confirmed bookings
(the ones you're actually running) and hide the rest.
## Sort
Four options, controlled from the Sort dropdown:
* **Priority** — highest priority first, then time anchor ascending. The default.
* **Time anchor** — soonest date first, regardless of priority.
* **Added to triage** — most recently surfaced first. Useful for "what showed up today" after clearing the morning batch.
* **Entity type** — groups runs, action items, invitations, and integrations together.
## Group
Orthogonal to sort. The group dropdown stacks entries under headers:
* **No grouping** — flat list.
* **Time horizon** — buckets entries by when their anchor falls (Today, This week, Later, plus Anchorless for signals without a time anchor).
* **Entity type** — Action items / Runs / Guide invitations / Integrations.
* **Experience** — groups everything tied to the same experience together.
* **Run** — groups everything tied to the same run together.
Combining **sort: Priority** with **group: Run** is a common pattern — you see urgent entries at the top, with the rest of the same run's entries clustered underneath.
## Horizon
The horizon dropdown controls how far into the future Triage looks. Entries whose time anchor is beyond the horizon are hidden. Signals without a time anchor (integration sync failures) show regardless.
* Presets: **3 days**, **1 week**, **2 weeks** (default), **1 month**, **3 months**
* Or pick any future date from the calendar — the horizon becomes "between now and that date"
A narrower horizon is more satisfying. Most agencies land on 1 or 2 weeks
because that's roughly the window where something *can* be actioned before
the run happens.
## Snoozing
Snooze any entry from the detail panel on the right, after selecting its row. Snoozes are **personal** — they hide the entry from you, not from your teammates.
Fixed set, no custom datetime:
* **1 hour** — a short break
* **4 hours** — half a day
* **Tomorrow, 8:00** — clears it until 8am tomorrow in your local time
* **Next Monday, 8:00** — handy on Fridays for a clean Monday morning
Each option shows the exact resulting datetime alongside the label, so
there's no ambiguity about when the entry comes back.
Turn on **Show snoozed** in the filter menu. Snoozed entries appear in
the list with a muted style and a chip showing when they'll un-snooze.
A snooze expires at its scheduled time and the entry reappears —
*unless* the underlying state was resolved in the meantime, in which
case the entry stays gone.
## Saved views
Views are how you preserve a useful filter combination without re-configuring it every time.
### Saving
Set up the state you want, then either:
* Right-click the **Everything** button and choose **Save current state as view…**
* Open the **Views** dropdown and click **Save current view…** at the bottom
Give the view a name and save. It now lives in your Views dropdown.
### Pinning
Click the star icon next to a view in the Views dropdown (or right-click the chip if it's active) to pin it. Pinned views appear as chips in the filter bar next to "Everything." Unpinning sends them back to the dropdown.
### Editing and deleting
Both actions are in the Views dropdown menu for each view, or in the right-click menu on a view's chip. Editing lets you rename; deleting removes the view permanently.
### Modifying an active view
When you load a view and then change something — a different sort, an added filter — the filter bar shows a small **Save** button. Click it to update the view with your changes, or leave it to keep the change as a one-off.
Saved views are **personal** — they aren't shared with your team. If
you want to show a specific view to a teammate, copy the page link and
send it to them: they'll see exactly what you see, no matter what they
had saved themselves.
## Sharing views and picking up where you left off
Two behaviors worth knowing:
**Helm remembers what you had.** Close Triage and come back later — on the same computer, you'll land on whatever filters, sort, grouping, and horizon you had last time. No need to reconfigure.
**Links carry the whole view.** Whatever state you're looking at, copy the page link from your browser's address bar and send it. When a teammate opens it, they see exactly what you see — same filters, same sort, same horizon. This works even if they had something different saved themselves.
On a brand-new computer, Helm starts you off with a sensible default: the full view for admins and owners, and an **Assigned to me** filter for everyone else.
## Admin controls
Two admin-level configurations affect what Triage surfaces. Both live under **Settings → Organization**.
### Turning signals on or off
Navigate to **Settings → Organization → Triage**. You'll see every signal Helm supports with a toggle. Disabling a signal hides it from Triage for **every user in the organization**, not just you. Re-enabling brings it back instantly.
Disabling a signal doesn't "resolve" its entries — it hides them. The
underlying state (overdue items, unassigned runs, etc.) is still there in
your data. If you re-enable the signal later, everything that was
matching comes back.
Common reasons to disable a signal:
* **You haven't set up the data for it.** `run.missing-tickets`, for example, only fires on rates flagged "Requires tickets." If no rates are flagged, the signal never fires — safe to leave on. But if your organization doesn't use tickets at all, turning it off removes it from the admin list for clarity.
* **It's noisy for your workflow.** If your team resolves run inconsistencies through a different tool and doesn't want Triage to track them, turn it off.
* **You're piloting.** Disable most signals at first and enable them one at a time as your team adopts them.
### Configuring "Requires tickets"
For the **Missing tickets** signal to ever fire, you need to mark at least one rate as needing tickets. This is a per-rate setting, not per-organization.
Navigate to **Settings → Organization → Experiences**, open the experience, and open the rate you want to configure. You'll see a **Requires tickets** checkbox. Enable it and save.
From that point on:
* Every run booked on that rate that doesn't have a ticket uploaded surfaces in Triage under `run.missing-tickets`.
* Uploading any ticket to the run clears the entry.
* Toggling the setting off at any time makes the entries disappear immediately.
"Requires tickets" is a Triage signal input, not a booking-flow
validation. Helm won't block a booking on a ticketed rate just because
the ticket isn't uploaded — it just flags the run for attention.