Saved views & scheduled reports
Freeze a filter you keep re-typing, and let it email itself on a cadence.
Two small features that remove a recurring chore: the filter you set up every Monday, and the export you paste into a deck every Friday.
Saved views
A saved view stores a name, a surface (calls, analytics or deals) and the query behind it: filters, date range, scope, search term.
- A view is personal by default.
- Marking it shared makes it visible to the whole org.
A shared view is a saved question, not a saved answer. It still runs under the read scope of whoever opens it, so sharing "Deals going quiet" with the team shows each manager their own teams' deals, and shows a rep only their own. Sharing a view can never leak rows.
Scheduled reports
A scheduled report is a saved query plus a delivery schedule:
| Field | Options |
|---|---|
| Cadence | daily, weekly, monthly |
| Recipients | Up to 50 email addresses |
| Format | csv (the raw rows) or summary (a readable digest) |
The hourly job runs reports that are due and emails them. As with digests, an unconfigured mail provider logs instead of sending rather than failing.
Use csv when the report feeds a spreadsheet or a BI tool, and summary when it goes to a person who wants the number in the body of the email.
Ad-hoc export
Every analytics module also supports ?format=csv directly, and the console has a download control on each one, for when you want the data once and don't want to schedule anything.
API
GET|POST|PATCH|DELETE /v1/saved-views and /v1/scheduled-reports.