Token activity

To audit token-based license usage at a granular level, open the Token activity report. It logs each transaction where users consume or request tokens, including feature usage, username, usage date, and the remaining available tokens.

In the product this report is the Token Activity sheet of the Disposable Token Management dashboard.

The following screenshot shows the log of token consumption events:

The Token Activity table, with one row per token consumption event.

Visualizations

The report has the following visualization:

• Token Activity Table: Use this table to see each token activity event.

Values displayed:

• Vendor: The provider of the token-based license.
• Server Name: The server that issued the tokens.
• Feature Name: The specific feature or application for which users consume tokens.
• Product Name: The product associated with the token transaction.
• Username: The user who consumes or attempts to consume tokens.
• Usage Date: The date when the token activity occurred.
• Tokens Consumed: Number of tokens the user consumed in that transaction.
• Tokens Available: Tokens that remained in the pool at the time of the transaction.

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 particular software features.
• User Name: Filter by specific usernames to view their token consumption history.
• Child Username: OpenLM Platform aggregates usage under a parent user account, so User Name shows the combined total for that person. Select a child username here to drill into a single account merged under the parent. See User aliases for how OpenLM Platform builds the mapping.
• 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.
• Server Name: Filter by the servers that issued the tokens.
• Token Type: Select the type of token if multiple token schemes are in place.

Interpreting this report

Use these points to read the report:

• This is the token ledger, with one row per consumption event, with the tokens taken and the pool balance (Tokens Available) at that moment. It is the audit layer under the aggregates in Token usage.
• Tokens Available falling toward zero is the number to watch: unlike floating licenses, an exhausted token pool stops everyone until you replenish it, and no queue forms for the missing tokens.
• Consumption events with no matching activity in the user's session reports deserve closer review - token draws are financial transactions, and this table holds each of them individually accountable.

Note

Token records can be sparse. The Date filter defaults to a short window, so widen it before you conclude that no consumption happened. Fields the license manager did not report read null.