Configure ZopNight team showback so every cloud dollar lands on the right team. Equal split for shared resources, unattributed bucket for the rest, trends and resource breakdowns per team.
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; Billing sync configured for accurate amortized or unblended cost; Teams created with resource assignments.
The steps
- Create teams and assign resource UIDs.
- Trigger a showback refresh.
- Open Reports and the Teams tab.
- Add tag attribution.
- Subscribe to weekly digest.
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 guide covers where it fits, and the AWS EC2 scheduling 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.
Questions we get a lot.
If yours isn't here, email us and we'll answer directly.
How are shared resources split across teams?
Equal split via shareCount. If a resource belongs to 3 teams, each team is attributed 1/3 of the cost. Unattributed resources are tracked separately so the totals always balance.
What is the difference between team showback and tag showback?
Team attribution splits cost equally across owning teams. Tag attribution gives the full cost to each tag key-value pair (no splitting). Both surface as separate dimension_type rows on cost_allocation_daily.