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

# Schedule reports and review report runs

> Understand scheduled report access, report runs, subscriptions, and why scheduling should preserve the same calculation and scope as the source report.

Scheduled reporting turns a repeatable report into a recurring delivery or run history. It is useful only when the saved report already has a clear calculation and scope.

## Scheduled access

The Reports navigation can expose a Scheduled or Runs section when the relevant feature flags, plan, and permissions allow it. Current Settings also gates some reporting administration to Teams owners or admins.

## What a scheduled report should preserve

A schedule should keep the report key or definition, period logic, data scope, filters, and recipient or delivery configuration consistent with the report you intended to automate.

Do not schedule a vague dashboard screenshot and assume it will always represent the same period or scope.

## Report runs

Runs provide history for scheduled or generated reports. Open a run detail when you need to understand what happened on a specific execution rather than editing the underlying report definition.

## Permissions

Viewing reports and exporting them are separate permissions. Scheduling can also be limited by plan and administrative access.

## Related articles

* [Build and save a report](/product/reports/build-report)
* [Use the report catalog](/product/reports/use-report-catalog)