---
title: Dashboards in Venom Tasks
description: Save an Insights chart with a name, keep it private or share it with the org, and see your saved insights as a grid of live charts on the Dashboards page or inside a Notes page.
section: cloud
order: 133
audience: [user, agent]
sources: [services/nodejs-cloud/components/tasks/insights/Dashboards.tsx, services/nodejs-cloud/components/tasks/insights/SaveInsight.tsx, services/nodejs-cloud/components/tasks/insights/SavedInsightChart.tsx, services/nodejs-cloud/components/tasks/insights/InsightBlock.tsx, services/nodejs-cloud/components/tasks/insights/saved-model.ts, services/nodejs-cloud/lib/tasks/saved-insights.ts, services/nodejs-cloud/lib/tasks/saved-insights-contract.ts, services/nodejs-cloud/migrations/0246_tasks_saved_insights.sql]
features: []
---

A saved insight is a chart from [Insights](/docs/cloud/tasks-insights.md) with a name: the view it was opened on (team, filters,
search text, saved view, sub-issues, subteams) and the panel's measure, slice, segment, chart and window. Saved insights
show on the **Dashboards** page in Tasks, and any of them can go in a Notes page next to Experiments' charts.

## Save an insight

1. Open **Insights** on a list, board, project, cycle or saved view, or from the sidebar.
2. Pick the chart you want, then press **Save insight** in the panel's header.
3. Name it. Tick **Share with the org** to show it to everyone in the organisation, or leave it unticked to keep it
   private. Press **Save**.

Opened from the Dashboards page, the panel's button says **Save**: it updates that insight with your current choices
(**Save as new** keeps the original). If someone else changed it after you opened it, Tasks says so instead of writing
over their change.

## The Dashboards page

**Dashboards** in the sidebar (`/tasks/dashboards`) shows the saved insights you can see as a grid: yours and the ones
shared with the org. **All**, **Shared** and **Private** narrow it.

- **Live.** Each chart is worked out when the page opens, when you come back to the tab, and when you press
  **Refresh**. Nothing is cached.
- **Size.** A tile is **Small**, **Medium** or **Large**: one, two or three columns wide on a desktop. On a tablet the
  grid has two columns and on a phone one, so every tile is full width there.
- **Order.** **Move earlier** and **Move later** in a tile's menu change its place for everyone who sees it.
- **Open.** A tile's name opens the full Insights panel on it, with the table and drill-down. Its **⋯ → Copy link**
  copies `/tasks/dashboards?insight=<id>`, which opens the same insight for anyone who can see it.
- **Share or make private, rename, delete.** In the tile's menu. A private insight's owner can change it; a shared one
  can be changed by its owner or by whoever manages Tasks (org owners and admins).
- **Copy block for a Notes page** copies the block described below.

Under the grid, **Pages with live insights** lists the Notes pages that hold insight blocks (the same list as the
`globe_dashboard_list` tool). A page of several insights is a dashboard you can lay out with text around it.

## Who sees what

- A **private** insight is seen only by the person who saved it.
- A **shared** insight is seen by everyone in the organisation who has Venom Tasks, with one exception: if it is about
  a private team (it names the team, a saved view or cycle of that team, a project that belongs only to private teams,
  or the team in an advanced filter), people who can't see that team don't see the insight at all, not even its name.
- **Numbers are always counted as the reader.** A shared chart of "every team" shows each person only the issues they
  may see, so nobody sees counts from a private team they're not in. A chart about "my issues" shows each reader their
  own.

## In a Notes page

Type `/insight` in a page. The picker lists Experiments' insights and, under **Venom Tasks**, your saved insights;
pick one. In markdown the block is:

````markdown
```insight
id: tasks-0b6c1f2e-1111-4222-8333-444455556666
```
````

The block is counted as whoever reads the page, as on the Dashboards page. It says **Insight unavailable** when the
insight was deleted, when it's about a team the reader can't see, or when the reader's organisation doesn't have Venom
Tasks.

## For agents and scripts

| | |
|---|---|
| `GET /tasks/api/saved-insights[?scope=personal\|workspace]` | the saved insights you can see, in the Dashboards page's order |
| `POST /tasks/api/saved-insights` | save one: `{name, query, scope?, scopeLabel?, size?, description?}`. `query` is the query string of `GET /tasks/api/insights` (for example `team=ENG&measure=cycleTime&slice=assignee&days=90`); paging, order and `drill` are dropped. `scope` is `personal` (the default) or `workspace` |
| `GET`, `PATCH`, `DELETE /tasks/api/saved-insights/{id}` | read, change (any create field, `position: {afterId?, beforeId?}`, and `expectVersion`: a stale one is `409 version_conflict`), delete. `{id}` may also be the block id `tasks-<id>` |
| `GET /tasks/api/saved-insights/{id}/result` | `{insight, result}`: the numbers now, counted as you (the same `result` as `GET /tasks/api/insights`) |

Each insight carries `id`, `name`, `description`, `scope`, `ownerId`, `query`, `scopeLabel`, `size` (`small`, `medium`,
`large`), `version`, `canEdit` and `blockId`. The MCP tools on `/tasks/mcp` are the same routes, as the caller:
`tasks_saved_insight_list`, `tasks_saved_insight_create`, `tasks_saved_insight_get`, `tasks_saved_insight_run`,
`tasks_saved_insight_update` and `tasks_saved_insight_delete`. To put one in a page, write the block above with
`globe_note_write` or `globe_note_edit`; `globe_dashboard_list` lists the pages that hold insights.

```bash
# Save a shared chart of cycle time per assignee in ENG, from a signed-in session.
curl -s -b "venom_cloud_session=…" -H 'content-type: application/json' \
  -d '{"name":"ENG cycle time by assignee","query":"team=ENG&measure=cycleTime&slice=assignee&days=90","scope":"workspace"}' \
  https://cloud.usevenom.dev/tasks/api/saved-insights
```
