Session details

To see how many license sessions each feature, user, group, or project has, open the Session details report. It tracks the total number of license sessions to help you identify user behavior, feature demand, and licensing trends for capacity planning and optimization.

In the product this report is the Session Report sheet of the Feature Insights dashboard.

The following screenshot shows the charts of session totals by feature, user, group, and project:

The Session details report tracks license sessions to monitor usage patterns and support capacity planning.

Visualizations

The report has the following visualizations:

• Total Number of Sessions by Feature Names: Use it to see the total count of sessions for each feature. Values displayed:
  • Feature Names
  • Total Number of Sessions
• Total Number of Sessions by Usernames: Use it to see the total count of sessions for each user. Values displayed:
  • Usernames
  • Total Number of Sessions
• Total Number of Sessions by Group Names: Use it to see the total count of sessions for each group. Values displayed:
  • Group Names
  • Total Number of Sessions
• Total Number of Sessions by Project Names: Use it to see the total count of sessions for each project. Values displayed:
  • Project Names
  • Total Number of Sessions

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.
• Day of Week: Select specific weekdays.
• Feature Name: Select specific licensed features.
• 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 specific users.
• Child Username: OpenLM Platform combines usage under a parent user account, so User Name shows the combined total for that person. Select a child username here to drill down into a single account merged under the parent. See User aliases for how OpenLM Platform builds the mapping.
• Group Name: Select groups.
• Project Name: Select projects.

Interpreting this report

Use these points to read the report:

• Session counts measure demand events, not workload. 1,000 sessions of 10 minutes and 10 sessions of 100 hours are the same usage time but different stories. The former pattern (frequent short checkouts) creates license churn and benefits from pool headroom. The latter risks holding licenses idle. Read this report against the hours in Feature usage per group.
• By-user session counts expose behavior. One user with an order of magnitude more sessions than peers is either scripting license checkouts or fighting an unstable application. Both are worth knowing.
• The group and project charts attribute session volume the same way the usage reports attribute hours. A project heavy here but light in usage hours runs many brief sessions, which is typical of validation or batch workflows.