Token usage
The Token Usage Report provides insights into how users consume software tokens across dates, users, and features. Tokens represent license usage credits for various software features, and this report helps track peak usage, identify top consumers, and monitor usage patterns to support resource planning.
In the product this report is the Token Usage Report sheet of the Disposable Token Management dashboard.
Token Usage
A detailed report visualizing token consumption trends across dates, users, and features for efficient license resource management.
Visualizations
- Token Usage by Date Bar Chart: Displays the maximum number of tokens that users consume on each day of the selected period, helping you track daily peak loads.
Values displayed:
-
Date
-
Maximum number of Tokens
-
Token Usage by User Bar Chart: Highlights how many tokens each user consumes, showing top token consumers.
Values displayed:
-
Username
-
Maximum number of Tokens
-
Token Usage by Feature Bar Chart: Shows the number of tokens users consume for each feature or application, allowing analysis of feature-specific usage.
Values displayed:
-
Feature Name
-
Maximum number of Tokens
-
Filters:
-
Date: A relative date filter. It defaults to Last 14 days and prints the resolved range underneath (for example,
2026/07/11 to 2026/07/24). Select another preset, or a custom start and end date, to change the reporting period. -
Feature Name: Users can filter the data based on specific feature names.
-
Software Name: Select a catalogued product from the SAM Catalog. The catalog normalizes publisher and product names, so filtering here groups license records that carry inconsistent raw license strings.
-
User Name: Users can select particular users to check their token usage activity.
-
Server Name: Users can select specific servers to analyze where the token requests originated.
-
Token Type: Users can filter by different token types if multiple token schemes are in place.
-
Product Name: Users can narrow down usage by specific products linked to the tokens.
Interpreting this report
- Token licensing spends a shared pool, so this report is a burn-rate view. The daily chart's peaks are the days work cost the most tokens - align them with deadlines and batch runs to know whether peaks are structural or incidental.
- The by-user chart is the consumption ranking: token models make cost per user explicit, and the top consumers here are the accounts to check first when the pool drains faster than planned.
- By-feature consumption prices each application in tokens - a feature drawing a large share of tokens for marginal use is the strongest candidate to move to (or from) token licensing at renewal.
- Version 25 carried an equivalent report family for Autodesk TokenFlex; the Platform's disposable-token reports generalize the same reading - consumption against a prepaid pool - across vendors.
This report only has something to show once OpenLM has collected disposable-token transactions. Widening the Date filter does not help when OpenLM has collected no token data at all - the visuals stay on No data. This screenshot uses a 20-year filter window to make that clear.