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

# Give every team its own cost report

> Scope automated cost reports to each engineering team and deliver them by Slack, Teams, or email, with no billing console access needed.

When FinOps sits with one person, every other team is blind to its own cloud spend. Cost-saving work is hard to track, teams can't see the impact of their changes, and the FinOps owner becomes a bottleneck.

This guide scopes automated cost reports to each team using Costory's [Slack, Teams, and email reports](https://docs.costory.io/features/slack-reports.md), so every squad sees its own costs.

[Embedded content](https://cdn.lottielab.com/l/8n9YWopevrhfb6.html)

## Prerequisites

* Your cloud billing data is connected to Costory (see [Quickstart](https://docs.costory.io/get-started/quickstart.md)).
* You have a way to scope costs per team, either via native cloud tags, via [dimensions](https://docs.costory.io/features/tagging/dimensions.md) that map resources to teams, or via [Teams](https://docs.costory.io/features/teams.md) with persistent cost scopes.

## What you get

* Per-team cost reports delivered automatically via Slack, Teams, or email.
* Each squad sees only the data relevant to them. No noise, no manual digging.
* A continuous feedback loop that keeps teams accountable for their cloud spend.

## How to set up per-team cost reports step by step

**1. Scope a view to a team**

Open any view in [Explorer](https://docs.costory.io/features/cost-explorer.md) and filter to the scope you want to report on: a specific team, service, or environment.

Reports can be scoped using:

* **CSP metadata:** cloud provider attributes like service name, region, or account
* **Native labels:** your existing cloud resource tags
* **Dimensions:** imported tags and rule-based mappings to teams, environments, features, or custom groupings via [Dimensions](https://docs.costory.io/features/tagging/dimensions.md)

![Per-team cost report](https://mintcdn.com/costory/VgOY4BJyTDVknUpv/images/decentralize-finops.png?fit=max\&auto=format\&n=VgOY4BJyTDVknUpv\&q=85\&s=43b87b7798177cabed4903306c1e4352)

Per-team cost report, scoped to a specific squad

**2. Schedule automated delivery**

Create a scheduled report from your current view. Configure the delivery channel (Slack, Teams, or email) and set the cadence: weekly or monthly.

Reports run automatically, giving teams a continuous feedback loop.

![Scheduling a per-team cost report](https://mintcdn.com/costory/J5jsJ0PTkezEIw4l/images/decentralize-finops.gif?s=b708f5af620fd032568e3040bfcfbf85)

Scheduling a report from Explorer

For example: your backend team gets a weekly Slack report scoped to their services, your data team gets one scoped to BigQuery and Datadog, and leadership gets a monthly summary across everything.

> [!TIP]
>
> You can set up each team's report from chat with the [Costory MCP](https://docs.costory.io/features/mcp.md): "schedule a weekly Slack report of the backend team's costs to their channel."

**3. Iterate and expand coverage**

Start with one or two teams, validate the report content, then roll out to all squads. Combine with [budgets](https://docs.costory.io/use-cases/automate_budget.md) to add spending alerts alongside the reports.

## Next steps

* **Add event context to team reports:** Connect [events](https://docs.costory.io/setup/events) so each team sees deploys and incidents alongside their costs. See [Event Correlations](https://docs.costory.io/automate-reporting/event-correlation.md).
* **Include unit economics:** Show teams their cost per user or per request, not just total spend. See [Relate Costs to Usage](https://docs.costory.io/automate-reporting/unit-economics.md).
* **Automate the monthly review:** Use the [Digest](https://docs.costory.io/features/digest.md) for AI-generated org-wide reports. See [Monthly Cloud Cost Reporting](https://docs.costory.io/automate-reporting/monthly-reviews.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.