Credit Consumption
The Credit Consumption tab (My Account) is the team-admin dashboard for credit usage across your team and its sub-teams for the current reporting period.
Only team admins can open this tab.
It answers: How much of our shared pool has this part of the org used — and who is close to a ceiling?
Credit Consumption (billing credits across the subtree) is different from the Usage tab (token analytics). Use Credit Consumption for allocation and governance; use Usage for detailed token reporting.
What You See​
Summary Cards​
Typical figures include consumption, allocation, remaining headroom, and utilization for the scoped subtree.
Near Their Allocation​
Teams approaching (or exhausting) their credit ceiling are called out so you do not have to scan a deep hierarchy for risk.
By Team​
A table of the current team and nested sub-teams with allocation and utilization.
A sub-team that was deleted stays in the table, labelled (deleted), because its usage this period still counts against the teams above it. It also appears in the drilldown by team.
Trends​
Credit consumption over time, with selectable granularity.
Drilldown​
Break usage down by:
| Dimension | Use it to see… |
|---|---|
| Team | Which sub-teams consume the most |
| Project | Which projects draw the most |
| Member | Which people consume the most |
| Model | Which models drive cost |
Email Digest​
Configure a Scheduled digest so a periodic credit summary for the subtree arrives by email.
| Setting | What it does |
|---|---|
| Frequency | Daily, Weekly (Mondays) or Monthly (the 1st), sent at about 06:00 UTC. Off by default. |
| Include sub-teams | Roll up the team's whole branch, rather than its own usage alone. |
| Recipients | Comma-separated email addresses, up to 20. Leave it empty to send the digest to the team's owner and admins, looked up each time a digest is sent. |
The digest is sent with the branding of the site the settings were last saved from. If your organization uses a white-label version of the platform, save the digest settings from that site. A team with its own subdomain always uses that subdomain's branding.
How This Relates to Caps​
| Control | Where you set it | What it does |
|---|---|---|
| Sub-team credit cap | Sub-teams | Ceiling on that team + its descendants |
| Project credit allocation | Project Billing | Ceiling on one project's draw from the team pool |
| User credit limits | Team Settings | Per-user limits (separate from team/project ceilings) |
When a ceiling is hit, further agentic work that requires credits can be blocked until an admin raises the limit or the period resets.
Who Can View It​
Team admins (including inherited parent admins) for the subtree in scope. Members and editors do not get this admin dashboard.