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

# Reports

> Generate, schedule, deliver, and share dashboard or saved-query reports.

Open **Reports** to manage report schedules, generation history, and reusable templates.

## Choose content

A report uses a dashboard or saved view as the source. Templates define a reusable source type,
format, and content defaults; a schedule binds the template to a concrete resource.

Built-in template patterns include platform health, RUM experience, alert review, SLA compliance,
and saved-query exports.

## Choose a format

| Format | Typical use                                             |
| ------ | ------------------------------------------------------- |
| PDF    | Headless rendering of the dashboard or saved view.      |
| PNG    | Headless image rendering for collaboration tools.       |
| CSV    | Current static report-metadata payload in tabular form. |
| JSON   | Current static report-metadata payload for automation.  |
| SVG    | Current static report summary card.                     |

PDF and PNG require the headless renderer. Configure
`[scheduled_reports.renderer]` with a reachable web base URL. The server validates generated file
signatures instead of returning placeholder content. CSV, JSON, and SVG currently contain report
metadata rather than executed dashboard or saved-view rows.

## Schedule and deliver

Configure the data range, an `every:<n><s|m|h|d>` interval, output format, and one or more
recipients. Although the API field is named `cron`, five-field cron expressions are not parsed;
an unrecognized value currently falls back to a 24-hour interval. Recipient kinds are:

* `webhook`, which POSTs the generated bytes to an HTTP(S) URL;
* `s3`, which writes to an object-key prefix in MoleSignal's configured object store;
* `email`, which currently validates and records the address but does not send SMTP mail.

Each recipient has an independent delivery record with status, attempt count, and error details.
Pause a schedule without deleting the configuration.

<Warning>
  Do not rely on the current `email` recipient for delivery. Use a webhook or configured
  object-store prefix until scheduled-report SMTP delivery is wired.
</Warning>

## Export and share

Use **Export now** to generate a download from a saved report. Use **Share** to create an
authenticated, cross-workspace, or restricted public share. Public reports can require a password
and can be blocked from CSV download by workspace policy.

## Permissions

* `reports.read` views schedules, templates, and history.
* `reports.create` creates reports.
* `reports.edit` updates content and delivery.
* `reports.schedule` enables, pauses, or runs schedules.
* `reports.delete` removes reports.

<Card title="Resource sharing" icon="share-nodes" href="/en-US/resource-sharing">
  Learn how public links, cross-workspace grants, expiration, and revocation work.
</Card>