Live Dashboards

Live Dashboards turn Dawn output into interactive views that teams can revisit, refresh, and share from the same workspace context that produced them.

What Live Dashboards Are

A Live Dashboard is a Dawn-generated interactive view. Use one when a static message or markdown file is not enough and the team needs filters, tables, charts, cards, or a small operational surface that can be reopened later.

Good examples include launch readiness trackers, customer-health views, campaign status boards, support queue summaries, PR review rollups, lightweight analytics reports, and one-off dashboards that help a team understand current state.

Where The Data Comes From

Dashboards can be built from the context the selected agent can already use:

  • conversation messages and thread context;
  • workspace files and generated files;
  • attachments referenced in the current conversation;
  • connected sources assigned to the agent;
  • workspace memory and skills that shape how the agent should interpret the work;
  • personal sources only when the signed-in user explicitly uses them and the share mode allows it.

Dawn does not bypass the agent’s permissions. If an agent cannot read a file, source, or private connection during a normal run, it cannot use that data to build a dashboard either.

Draft, Preview, And Publish

The usual flow is:

  1. Ask Dawn to create a dashboard for a focused job.
  2. Review the generated draft.
  3. Ask for revisions in plain language.
  4. Open the dashboard preview.
  5. Publish or share the dashboard when the view is ready.

Keep the first version narrow. A dashboard that answers one operational question well is easier to trust than a broad dashboard that tries to model the whole workspace.

Share Modes

Live Dashboard sharing should match the source data.

  • Private draft: useful while the owner is iterating.
  • Workspace share: useful for views built from workspace-visible files, sources, and generated data.
  • Restricted share: useful when only specific workspace roles should see the dashboard.

Avoid publishing dashboards that depend on private personal connections unless the view is intentionally private to that user.

Updating A Dashboard

Live Dashboards are designed to be revised. Ask Dawn for targeted changes:

Make the risk table the first section and add a status filter.
Use the latest generated CSV instead of the old attachment.
Split customer health into green, amber, and red groups.

The dashboard should stay connected to the workspace artifacts it was built from, so generated outputs can be reused instead of copied into a separate system.

Safety And Limits

  • Dashboards are not a replacement for source systems of record.
  • Shared dashboards should not expose personal-source data to the workspace.
  • Large or slow datasets should be narrowed before publishing.
  • If a dashboard is built from generated files, keep those files available in the workspace.
  • If a source connection is removed or the viewer lacks permission, the dashboard may not be able to refresh that data.

Troubleshooting

  • Dashboard cannot load: confirm the viewer has access to the workspace and any shared dashboard restrictions.
  • Data is missing: confirm the selected agent can read the underlying file, source, or generated artifact.
  • A private file fails after sharing: rebuild the dashboard from workspace files or publish it as a private dashboard.
  • The dashboard is stale: ask Dawn to refresh the underlying dataset or revise the dashboard from current files.
  • Publishing fails: confirm the dashboard has a current revision and the user has permission to share it.