> ## Documentation Index
> Fetch the complete documentation index at: https://chatobserver.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Reports

> Build, organize, and share stakeholder-ready views of Chatobserver data.

# Reports

Reports are the layer you use when raw dashboard exploration needs to become something shareable and repeatable.

## What reports are for

Use reports when you want to:

* package a specific visibility story for stakeholders
* create repeatable views for a team
* control what readers can see
* share data without giving full workspace access

## Report structure

Reports are organized into pages and blocks. That makes them flexible enough for executive summaries, recurring performance reviews, or focused analysis on a single topic.

## Visibility and ownership

Reports can be scoped differently depending on who should see them. In practice, teams commonly separate:

* personal or private working reports
* shared workspace reports

Keep rough drafts private until the framing is ready.

## Sharing snapshots

Shared reports are delivered as read-only snapshots. A snapshot is useful when you need a stable link for stakeholders, because the shared view reflects the report state captured at the time the link was generated.

That also means a shared snapshot does not automatically update just because the underlying workspace changes.

## Viewer controls

Reports support author-controlled decisions about what viewers can adjust. That matters when you want one audience to explore and another to stay locked to the exact narrative you prepared.

## Good reporting practice

Strong reports usually:

* focus on one decision or question per page
* use a clearly defined time window
* avoid mixing exploratory views with executive summaries
* regenerate shared snapshots after meaningful edits

If a report is trying to do everything at once, it is usually better as multiple pages or multiple reports.