Token activity

The Token Activity Report provides a detailed log of individual token consumption events. It tracks each transaction where users consume or request tokens, including feature usage, username, usage date, and the remaining available tokens. This helps audit token-based license usage at a granular level.

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

Token Activity

A detailed log view that tracks each token consumption event by user, feature, and date for transparent licensing audits.

Visualizations

• Token Activity Table: This table provides detailed data showing 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.

• 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 results based on particular software features.

• User Name: Users can filter by specific usernames to view their token consumption history.

• Child Username: OpenLM 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 builds the mapping.

• 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.

• Server Name: Users can narrow down the activity to specific servers that issued the tokens.

• Token Type: Users can select the type of token if multiple token schemes are in place.

Interpreting this report

• This is the token ledger - 1 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 - no queue forms for a token that no longer exists.
• 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 are often sparse. The Date filter defaults to a short window, so widen it before you conclude that no consumption happened - this screenshot uses Last 5 years. Fields the license manager did not report read null.