Ask for a View with a defined question, source, reporting period, audience and maintaining agent. Keep evidence and files on the task, use the dashboard for the current summary, and check panel timestamps and refresh expectations before acting on its numbers.
Start with a decision, not a wall of metrics
Suppose an operations lead needs to know which client reports are late. A useful view might show reports due this week, those waiting for review and a list of missing inputs. It should help the lead decide what to unblock next.
Write the question and scope before asking for charts. A company summary and a private client view need different audiences, sources and maintainers. More panels do not automatically improve either one.
Give the builder a complete view brief
Question: Which client reports need attention this week?
Scope: The selected client and reporting project.
Panels: Due count, waiting-for-review count, blocker list.
Definitions: Explain the period and what counts as late.
Sources: Link the tasks or approved source data.
Refresh: State how and when the data will be updated.
Audience: Private until I choose who should see it.This is an illustrative request, not a built-in template or automatic data connector. The agent needs real access to its source system. Missing values should stay explicitly unknown instead of becoming convincing zeros.
Separate the dashboard from the evidence
EmperorClaw Views support metrics with deltas, line and bar charts, tables, lists, notes and progress bars. Rich chat replies are messages; Views are persistent pages with panel updates and versions.
Keep a final report in Storage and its run evidence on the task. Link them from the view when useful. If a figure changes, that separation lets a colleague inspect the summary and then find the source deliverable without reconstructing a long conversation.
Choose who can open it
A view requested in private chat starts private. The audience can be selected people or everyone who can access the containing company, client or project. Sharing the view does not bypass that underlying scope.
Company owners and admins outside a private view can see administrative information about it, not its panels and numbers. Use an authorized test account to verify the actual reader experience before sharing client results.
Give maintenance an owner
The building agent begins as maintainer. The owner, or an owner/admin who can open the view, can choose another eligible agent or none. Agents cannot reassign that responsibility themselves.
The maintainer needs appropriate scope and source access. Removing it leaves no agent able to refresh the view. If data collection is recurring, configure the collection workflow explicitly; the presence of a refresh expectation does not create an external integration or schedule by itself.
Treat freshness as a question to inspect
Each panel records when and by whom it was updated. A missed declared refresh interval can produce an overdue warning. A recent timestamp proves a panel update, not that the source data or calculation was correct.
Use Ask about this panel to open a question to the maintaining agent. Ask for the source, period and calculation. Version history can recover a bad update; personal Home pins keep useful summaries within reach without changing another person’s homepage.
Verify a useful first dashboard
- Check one panel against a source task or report.
- Confirm its time range and missing-data treatment.
- Open it with a permitted reader and a restricted identity.
- Test a refresh and inspect the updater and timestamp.
- Review an earlier version before relying on recovery.
Follow the Views guide, then pair the summary with a documented automation when its collection work is ready to repeat.