Saved reports

When you’ve built a report you’ll want again — this month’s spend by service, or a tag-coverage view for a specific team — save its configuration instead of rebuilding it each time.

What gets saved

A saved report stores the configuration, not a frozen snapshot: its name and description and the full builder setup — the dimensions you group by, the metrics, the account, service, and cost-center filters, and the time range and granularity. When you open it, it runs against your current cost data, so the numbers are always up to date.

Every report also carries its coverage: the exact integrations it was reading when you saved it. Coverage is a fixed selection — connecting a new AWS account later never changes an existing report. That’s deliberate: a saved report is often something teammates receive on a schedule, and its numbers shouldn’t quietly widen because the organization grew. To grow (or shrink) a report, open it, adjust the scope bar to the integrations it should cover, and Update it — the report re-freezes to your new selection, and the save dialog always states exactly what it will cover. If you disconnect an integration, reports simply drop it from their coverage; a report whose last covered integration is disconnected is removed with it.

Managing saved reports

Your saved reports live together as your organization’s custom report library, so anyone on your team can open a report a colleague built. Each one keeps the grouping, filters, and scope it was saved with, ready to run, export, or adjust and re-save. Anyone in the organization can open and run them; creating, editing, or deleting a saved report takes the Contributor role or above.

Is there a report you check first every time? Pin it from its card in the gallery and it opens automatically whenever you land on Reports. The pin is yours alone — it doesn’t change what teammates see, and it’s kept per browser, so set it again on a second machine.

They’re never more than a click away: the sidebar’s Reports entry expands into a menu with Report Builder on top and your saved reports listed beneath it — opening one from anywhere in the app switches the scope to the report’s own coverage. Inside the Reports gallery, each card is badged with its coverage (an integration’s name, or how many integrations it spans) whenever that differs from your current selection, and opening such a card re-pins the scope for you.

Plan limits

You can keep five saved reports on the Free plan. That’s enough for the handful of views most teams check regularly. Paid plans remove the cap so you can maintain a full library — a report per team, environment, or cost center — without pruning.

Next steps

Not sure what to save? Start in the report builder and save the views you find yourself rebuilding.
Put a report on autopilot with a scheduled report email — a recurring recap in your inbox, Slack, or Teams.
Query your saved reports in plain language through the CloudQuell MCP server.