Saved view embeds
A saved view embed puts a live PM, CRM, or Support list inside a document — not a screenshot, a live view with current data rendered whenever the doc is read.
What can be embedded
Module | Views |
|---|---|
PM | Task views from the PM module |
CRM | All deals · All contacts · All companies |
Support | Open conversations · Unassigned conversations · AI-active conversations |
The embed card shows the module label (PM / CRM / Support), the view name, and a summary of its filters (for example, open items only, 5 rows).
Inserting one
Slash menu → Saved View.
Pick the module, then the view.
The card renders live rows (capped to a small page size, e.g. 5) with a link to open the full view in its module.
Why embed views
Live dashboards inside docs — a weekly ops doc that always shows current unassigned conversations; a launch doc with the live deal pipeline.
Runbooks — an incident doc embedding "AI-active conversations" so responders see the current blast radius.
Reviews — a QBR doc embedding the current CRM pipeline snapshot without exporting CSVs.
Access and safety
The embed renders only what the reader can access: it's a live query in the reader's permission context, not a frozen export.
Saved view embeds are excluded from public help center rendering — they're for internal docs only, so customer-facing pages never expose internal lists.
The card links back to the source module view for the full list.
Was this article helpful?