> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/operate-and-troubleshoot/schedule-dashboard-summary-emails.md).

# Schedule dashboard summary emails

Use Dashboard Summary Mail for periodic reporting to a defined audience. Use operational alert rules when a recipient needs a notification about a particular event.

### Before you start

* Have permission to configure dashboard summaries.
* Select the dashboards the audience should receive.
* Confirm the recipients and reporting frequency.
* Check that the summary contains information appropriate for those recipients.

### Create a summary configuration

1\. Open Settings → Dashboard Summary Mail and select Add configuration.

2\. Enter Configuration name. Use Add description (optional) if a description is needed.

3\. Enter each approved To address and press Enter or comma to add it. Add CC (optional) only for intended copy recipients.

<figure><img src="https://3857940684-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJcSHU5jP5GABQrGmWvW2%2Fuploads%2FEa7ZIPiBzOi3xsVOEEeB%2Fsummary-mail-form.jpg?alt=media" alt="Add recipients explicitly, choose a reporting frequency and select the dashboards to include. The shown form was not saved."><figcaption><p>Add recipients explicitly, choose a reporting frequency and select the dashboards to include. The shown form was not saved.</p></figcaption></figure>

4\. Select Summary frequency: Weekly sends the previous week at the start of a week; Monthly sends the previous month at the start of a month; Yearly sends the previous year at the start of a year, as described by the form.

5\. Select at least one dashboard from the Dashboards list. The initial inspected form did not show a separate Default Dashboard selector; configure one only if it appears in the selected state/version.

6\. Review recipients and dashboards before Save. After saving an approved schedule, reopen its entry and check its next send date. The form was inspected without saving a new summary in this documentation walkthrough.

### Verify delivery

1. Check the next scheduled date displayed by the configuration.
2. After that time, confirm receipt with an intended recipient.
3. Compare the summary period and metrics with the underlying dashboard.
4. Open the dashboard link using the intended recipient access path.
5. Check the expiry information displayed with the link.

Do not assume that a generated email or link is permanently accessible. Share information through the access model appropriate to the recipient.

### Maintain the schedule

* Use **Edit**, update the configuration, and select **Save**.
* Verify the next send date after a frequency change.
* To stop future summaries, remove the intended configuration using **Delete** and confirm the result.

### Expected result

The intended audience receives a summary for the configured reporting period and can use the supplied dashboard link.

### Troubleshoot

* Cannot save: check the required name, To recipients and dashboard selection. If your selected state exposes a default-dashboard control, confirm its value is included.
* Wrong dashboard opens: review the selected dashboards and any default selector exposed by your version.
* Summary missing: check the configuration's next date, recipient address, delivery records, and quarantine.
* Figures differ: align the dashboard, reporting period, filters, and timezone before comparing.
* Link expired or access denied: use the current access route or contact the dashboard administrator.

### Worked setup: a single-dashboard weekly summary

Use one approved dashboard and a defined audience. The inspected form offered Automation Operations, Banking Dashboard, Executive Overview and Financial Impact; available dashboards depend on the environment.

1\. Enter a descriptive configuration name and only approved To/CC recipients.

2\. Select Weekly and one intended dashboard, for example Automation Operations when that is the agreed report. Do not use a dummy recipient in a saved schedule.

3\. Before Save, check that the audience is permitted to see that dashboard’s data. If this is only a setup review, choose Cancel instead.

4\. After an approved save, record the next send date. Confirm actual receipt after that date and compare the report’s period and values with the same dashboard.

The inspected existing System Default Dashboard Summary Email had a next-send date of 1 November 2026. That is evidence of an existing schedule’s displayed date, not evidence of future delivery or of a newly created test configuration.