# How to Set Up Team-Level Cloud Budgets: Step by Step

> How to Set Up Team-Level Cloud Budgets. A practical walkthrough with ZopNight: read-only setup, production excluded by default, reversible at every step.

Source: https://zop.dev/learn/how-to/set-up-team-budgets
Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, how-to, learn

---

Configure per-team cloud budgets with tiered alerts in ZopNight. Drive cost accountability by giving every team visibility into their cloud spending.

This is the practical version, the one you can follow in a single sitting. It starts read-only, touches no production resource by default, and every step is reversible, so there is no point at which you are committed to something you cannot undo. Budget about 30 minutes. Before you start you will want: Cloud accounts connected with team-level tagging; Agreement on budget ownership; Notification channels configured.

## The steps

1. Analyze per-team spending.
2. Set realistic budget targets.
3. Configure tiered alert thresholds.
4. Route alerts to the right people.
5. Review and adjust quarterly.

## Why this is safe to do today

The reason this is a low-stakes change is that nothing here is destructive. Scheduling stops and starts resources; it never deletes them, and your data persists across a stop exactly as it does across a normal reboot. Production is excluded by default, actions run in dependency order, and every state change is logged with what triggered it.

If you want the fuller context behind this task, the [FinOps](https://zop.dev/learn/finops) guide covers where it fits, and the [AWS EC2 scheduling](https://zop.dev/zopnight/aws/ec2) page shows the same loop applied to a specific resource.

## Getting started

Getting started is intentionally low-stakes:

- Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage.
- Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status.
- Create a schedule in your timezone and attach the non-production resources or groups you want it to cover.
- Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing.

Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action.

## Frequently asked questions

### How do I handle shared infrastructure in team budgets?

Allocate shared costs proportionally based on each team compute spend. Be transparent about the allocation method. ZopNight supports configurable shared cost allocation rules.

### Should budget overages have consequences?

Start with transparency and conversation, not enforcement. Most teams self-correct once they see their spending data. Automated enforcement (like schedule tightening) should be a last resort for chronic overages on non-production resources.