What the console shows, and to whom
The Platform Consumption Console is the dashboard in your Workday tenant that shows how much of Workday's metered offers your organization has used. Every customer sees API requests and document storage there; customers on the Universal Main Subscription Agreement (UMSA) also see agent usage and their Flex Credit balance, because Flex Credits exist only under UMSA.
If your organization is on the Main Service Agreement (MSA), you get the storage and API views but no Flex Credit balance to look at. A missing balance there isn't a security problem. UMSA customers on the Complimentary Flex Credits Policy must sign the Workday Flex Credits and Platform Entitlement Policy to keep using Workday AI agents once the complimentary credits run out. How credits themselves work is covered in Flex Credits explained.
Who can open the console: the security domain
Access is controlled by one domain, Management Dashboard: Platform Consumption Console, in the System functional area. To grant it:
- Find the domain and choose Domain > Create Security Policy from its related actions.
- Select Confirm, then add security groups in the Report/Task Permissions grid with View.
- Run Activate Pending Security Policy Changes.
The same domain decides who receives the console's default credit alerts and who can run the Flex Credit Estimator task, so add finance or budget owners to it, not only administrators. Workday notes that the console's data is usage data and isn't treated as customer content.
How often the console's usage updates
Usage is not live. Workday updates it daily starting at 2:00 PM UTC with the previous day's usage, and the calculation can take up to 3 hours. If you test an agent at 10:00 UTC on Monday, look for it after about 17:00 UTC on Tuesday, not the same afternoon. The Developer Site's Entitlements dashboard is different: Workday aggregates its data every minute.
What each console page shows
Overview
The Embedded Entitlement Overview visualization shows how much of your baseline allowance you've used. Your policy includes an embedded entitlement; usage draws on that first. Only once it's exhausted does Workday charge usage against purchased credits, taking the credits that expire soonest first.
Consumption Usage
The breakdown by service. Workday measures three components:
| Component | What's counted | Charged in credits? |
|---|---|---|
| ComponentAgents | What's countedAgent skills and activities | Charged in credits?Yes, under the rate card |
| ComponentAPI Requests | What's countedNumber of API requests | Charged in credits?Only after you've signed the Workday Flex Credits and Platform Entitlement Policy; before that, informational |
| ComponentDocument Storage | What's countedGB stored | Charged in credits?No, but subject to service limits |
Workday's document limits page sets the ceiling at 10 TB, calculated in binary units, which the console reports as 10,240 GB. The Consumption Usage tab shows storage volume in total and by day. If your organization uses Workday Data Cloud, its entitlement and Flex Credit consumption also show in the console.
For agent detail beyond totals, Workday points to Agent System of Record. The Agent Analytics Hub report (secured by View: Agent Analytics Hub) pulls agent cost from the console alongside agent counts, conversations and monthly active users. Its cost section needs the console's domain as well.
Credit Balance and Credit Entitlement
Credit Balance shows daily Flex Credit activity. Credit Entitlement lists your credit packages with a status:
| Status | Meaning |
|---|---|
| StatusActive | MeaningAvailable to consume now |
| StatusInactive | MeaningPurchased, available from a future date |
| StatusExpired | MeaningNo longer usable |
Flex Credits are fungible across every offer on your rate card. When Workday adjusts your balance, the reason appears in an Adjustment Reason column on the All Packages grid; the column is absent if you've never had an adjustment.
Rate Card
The Rate Card page is Workday's stated definitive source for how usage converts to credits. Two columns matter: In Blocks of (Units), the number of units in one chargeable block, and Credit Rate per Block, the credits charged per block. Usage is charged by the block, so convert unit counts into blocks before you multiply by the rate.
If your signed policy version doesn't include platform components or entitlements, those entitlements and their usage don't appear on the console at all.
Flex Credit Estimator
Reached from Flex Credits > Credit Estimator or the Flex Credit Estimator task. It forecasts annual Flex Credit consumption from organization size, your Workday SKUs and the generally available agents and AI capabilities, then subtracts your platform entitlement for a net figure. You can export the estimate to Excel or PDF and, if eligible, buy Flex Credits from Marketplace. Workday labels estimates as informational, and the inputs aren't treated as customer data. The Flex Credits budget planning guide shows how to turn this into a budget.
Alerts and Budget
Two grids:
- Default Alerts. Workday notifies users with the console's domain when consumption reaches 80%, 90% and 100% of your active credit threshold, and shows a banner on the console.
- Alerts and Budgets. Custom alerts per agent against a weekly, monthly or annual credit budget. Pick recipients from users with the console's domain; if you pick none, everyone with the domain is notified.
Alerts don't stop anything. Workday states that the console doesn't deactivate offers when you exceed your entitlement. To stop an agent consuming credits, deactivate it in the Agent Management Hub.
Why Sandbox shows a balance you aren't charged
The console is enabled in Production and non-Production tenants. For most offers, non-Production usage is tracked and shown with an informational Flex Credit balance, but only Production usage is applied to your organization's balance.
Non-Production data is aggregated daily across all your non-Production environments. Open the console in Sandbox and you see the combined activity of Sandbox, Implementation and your other non-Production tenants, not Sandbox alone. Don't read a high Sandbox figure as one tenant's problem.
"For most offers" is Workday's wording, and the console documentation doesn't name the exceptions, so don't assume non-Production use of a given offer is free.
Standalone Adaptive Planning customers get a version of the console called the Agent Consumption dashboard inside their Adaptive Planning instance; it needs Planning Center permission.
What counts as an agent or tool invocation
For Extend and agent work, Workday's Invocation Definitions page names three units monitored in the console:
- Developer Agent invocation: a query or command to Developer Agent during Extend development, from the Developer Site or a supported third-party coding tool.
- Custom Agent invocation: processing in Workday's AI runtime for a request to a Production Extend app, on Base, Standard or Premium models.
- Tool calls to Agent-Ready Tools: from agentic Extend apps or external AI agents reading Workday data, or from agentic Extend apps reaching third-party systems through connectors. Each tool call is designated Base or Advanced in Workday's Tool Call Catalog.
The Developer Site has a separate Entitlements dashboard whose Organization AI Usage meter counts AI invocations against your allowance; use it alongside the console when the question is about Extend development rather than tenant-wide AI spend. Which meters that dashboard shows depends on your Extend package, as set out in Extend legacy vs Extend Professional.
Finding what drives API volume
The console gives API totals; the API Activity Report reports explain them. Workday delivers four: Monthly API Trends, Top 10 API Requests, Top 10 IP Addresses and Top 10 API Names, each filtered by the current user's billing ID and calculated on the first of the month for the month before. History builds automatically up to a 13-month rolling window. Workday notes these reports show data only for US and EU customers.
Start with Top 10 API Names to see which API dominates, then Top 10 IP Addresses to find which integration or system is sending it.