Saved views

Saved views remember the filters you set on a list page so you can come back to them in one click — without re-typing the same search, date range, or status combo every time.

They're available on:

• Leads (/leads)
• Contacts (/contacts)
• Accounts (/accounts)
• Tickets (/tickets)

Saving a view

1. Open one of the four list pages and apply the filters you want — anything in the filter bar (search box, dropdowns, date ranges) counts.
2. Open the view picker dropdown above the filter bar (it reads "All leads", "All tickets", etc., or "Custom view" if you've already applied filters).
3. Click Save as…, give the view a name (up to 80 characters), and decide whether to share it.
4. Click Save view.

Names must be unique within your own list of views for that entity. You can have a private "My open tickets" and a shared "Team escalations" — but you can't have two views called "My open tickets" on the same page.

Picking a view

Open the picker and click any view name. The page jumps to that view's filter combination immediately. The picker shows two sections when both apply:

• My views — every view you created, private or shared.
• Shared with team — views other admins have shared with the tenant.

The picker labels show:

• The active view's name when the current filters exactly match a saved view.
• "Custom view" when filters are applied but don't match any saved view.
• "All <entity>" when no filters are applied.

To clear back to the default unfiltered list, click All <entity> at the top of the dropdown.

Updating a view

If you tweak the filters on an active saved view and want to overwrite the saved version:

1. Open the picker.
2. Click Update current view.

The button is only available when the active view is one you own. Saved views shared by other teammates can't be edited from your account.

Sharing & unsharing

Sharing a view makes it visible to every admin in the tenant. They can apply it but they can't rename, retune, or delete it — only the owner can do that.

To share or unshare:

1. Open the picker → Manage views…
2. Find the view in the list and click Share (or Shared to remove sharing).

Unsharing doesn't delete the view; it just removes it from other teammates' pickers.

Renaming or deleting

In the Manage views… panel:

• Click Rename, type a new name, hit Enter (or Save).
• Click Delete to remove the view permanently. This can't be undone.

Both actions only work on views you own.

How saved views interact with the URL

Saved views write the same ?key=value query string the filter bar already uses, so:

• The URL after applying a view is the same shareable link as if you'd typed those filters by hand.
• Refreshing the page keeps the view active.
• Bookmarking is fine — bookmarks aren't tied to the saved view, only to the URL state.

If a view's stored filter includes a key the current page doesn't recognize (for example, after a Hydra update changes a filter name), the unknown key is ignored.

Bulk actions

Each list page (Leads, Contacts, Accounts, Tickets) has a checkbox column for selecting multiple rows. As soon as you check a row, a sticky action bar appears at the bottom of the screen with the operations you can run on the selection.

Selecting rows

• Row checkbox — toggles a single row.
• Header checkbox — selects/deselects every row currently visible on the page. If you've selected some but not all visible rows, it shows a mixed (indeterminate) state; clicking it selects all.
• Selection clears when you change filters. This is intentional — running an action on rows that aren't visible would be confusing and easy to do by accident. If you need to act on a different set, change the filters first, then re-select.
• The cap per call is 1000 rows. List pages display up to 200 at a time, so this is mostly a backend safety net.

Action bar

The bar floats above the page once at least one row is selected. The left-side × clears the selection. The middle shows how many rows are selected. The right side has the per-entity actions:

Stage / status / priority / reassign pickers are inline <select> dropdowns inside the action bar — pick a value and the action fires immediately. There's no separate confirm step for non-destructive bulk changes. Delete always opens a confirmation modal.

Bulk delete preview

Clicking Delete on any list opens a preview modal that fetches an impact summary for the selected rows. The summary tells you exactly what will happen to related data:

• "Will also be permanently deleted" — child rows that cascade with the parent. For example, deleting a ticket also deletes its replies and internal notes; deleting a contact also deletes its channel links and previously generated reports.
• "Kept but unlinked" — rows that survive but lose their reference. Conversations and tickets that pointed at a deleted contact stay in the system; their customer_id is just nulled out so the conversation history is preserved.
• "Cannot delete — clear these first" — only relevant on Accounts. Accounts with linked contacts or opportunities are blocked from deletion. Reassign or delete the related rows first, then try again.

The Confirm button is disabled when blockers are present. When the preview comes back clean (or with cascades/unlinks only), Confirm proceeds with the delete and the action bar clears.

Promote leads to contacts

The Promote to Contact… action on the Leads page opens a small dialog asking which Account to attach the new contacts to. This is required — every contact in Hydra has to belong to an account (it's a database constraint, enforced by the schema). After promotion the rows disappear from the Leads list and show up under the chosen account on the Contacts list.

Permissions

• Delete (any entity) and Promote are admin-only. Members signed in with a non-admin role won't see these actions, and the API rejects them with a 403 if invoked directly.
• Change status / priority / reassign on Tickets and Change stage on Accounts are available to any operational user — the bar mirrors the per-row actions you already had.

Audit trail

Every bulk action writes one row per affected entity to the admin audit log (visible at /team/audit-log). For deletions, the diff records the deleted entity's id; for status/priority/stage/reassign changes, the diff records the from/to values per row. Bulk operations are not condensed into a single log row — that means the log can grow quickly if you're routinely doing 50-row reassignments, but the trade-off is an exact per-record history when you need to investigate a specific change.