Custom query views are saved, named queries that produce filtered, sorted, grouped lists of records. They're how staff carve out the specific subset of data they need to work with day-to-day, without redefining filters every time.
What a View Defines
- Filters: Which rows to include (e.g. status=open).
- Sort: Order rows (e.g. by created date descending).
- Group: Optional grouping (e.g. by customer).
- Columns: Which fields to show.
- Column widths and order: Visual layout preferences.
- Page size: Rows per page.
- Sharing: Private, group, or organisation-wide.
Common Patterns
- “My open work”: Filter assignee=current_user, status=open.
- “Overdue items”: Filter due_date < today, status ≠ complete.
- “This week's signups”: Filter created_at within last 7 days.
- “Stale records”: Filter last_updated < 90 days ago, status=active.
- “VIP customers”: Filter total_spend > threshold, status=active.
Worked Examples
- Support agent's workspace: Three saved views — “My open tickets”, “All open tickets”, “Closed today”.
- Sales rep dashboard: “Hot leads” (qualified + recent activity), “Pipeline” (in any active stage), “Lost deals” (status=lost in last 30 days).
- Finance month-end: “Overdue invoices”, “Disputed transactions”, “Refunds pending”.
- Marketplace operations: “Vendors pending review”, “High-volume sellers”, “Recent disputes”.