Documentation / Reports

Reports

Report Notifications

When report-ready emails are sent and how the user preference affects delivery.

What this page is for

This page explains why report-ready emails exist, who receives them, and what has to be true before one is sent.

When to use it

Read this when:

  • you want to know whether the app should email you for completed reports
  • a report finished but no email arrived
  • you are deciding whether the notification should stay enabled

How it works

The notification is sent to the user who queued the review once:

  • the review completed
  • at least one report file exists
  • the user’s notification preference is enabled

The email includes:

  • the reports that were generated
  • high-level counts from consolidated findings
  • pillar scores for Operational Excellence, Reliability, Security, Performance Efficiency, and Cost Optimization
  • a link back to the review
  • one download link per generated report

If both the resource assessment and Landing Zone assessment were selected and generated successfully, the email shows both report downloads.

Why it exists

Reviews can take long enough that expecting users to sit on the review page is unrealistic, especially for large environments. The email is a re-entry point into the workflow.

What to expect

This is not an organization-wide alert by default. It is a per-user notification tied to the person who started the review.

Common mistakes

  • assuming every user in the org should receive the email
  • expecting the email before the report file exists
  • expecting a Landing Zone download link when Landing Zone assessment was not selected or did not generate a file
  • treating a missing email as a scan problem when it may really be a notification preference or mail delivery problem

Next step