Token usage

To see peak token use by date, user, and feature, open the Token usage report. Tokens represent license usage credits for various software features. Use the report to 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.

The following screenshot shows the token consumption charts:

Token consumption trends across dates, users, and features.

Visualizations

The report has the following visualizations:

• Token Usage by Date Bar Chart: Use this chart to see 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: Use this chart to see how many tokens each user consumes and who the top token consumers are.

Values displayed:

• Username

• Maximum number of Tokens

• Token Usage by Feature Bar Chart: Use this chart to see the number of tokens users consume for each feature or application and to analyze feature-specific usage.

Values displayed:

• Feature Name
• Maximum number of Tokens

To narrow the report, use these 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: Filter by specific feature names.
• Software Name: Select a cataloged 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: Select particular users to check their token usage activity.
• Server Name: Select specific servers to analyze where the token requests originated.
• Token Type: Filter by token type if multiple token schemes are in place.
• Product Name: Filter by the products linked to the tokens.

Interpreting this report

Use these points to read the report:

• Token licensing spends a shared pool, so this report shows how fast the pool is used. 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 is used up 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 26 carried an equivalent report family for Autodesk TokenFlex. The disposable-token reports in OpenLM Platform generalize the same reading, consumption against a prepaid pool, across vendors.

Note

This report only has something to show once OpenLM Platform has collected disposable-token transactions. Widening the Date filter does not help when OpenLM Platform has collected no token data at all: the visuals stay on No data.