Session details
The Session Report provides a detailed summary of how users, groups, and projects use licensed features over time. It tracks the total number of license sessions to help 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.
Session Details
Total number of license sessions tracked by feature, user, group, and project to monitor usage patterns and support capacity planning.
Visualizations
- Total Number of Sessions by Feature Names: Displays the total count of sessions for each feature.
Values displayed:
-
Feature Names
-
Total Number of Sessions
-
Total Number of Sessions by Usernames: Displays the total count of sessions for each user.
Values displayed:
-
Usernames
-
Total Number of Sessions
-
Total Number of Sessions by Group Names: Displays the total count of sessions for each group.
Values displayed:
-
Group Names
-
Total Number of Sessions
-
Total Number of Sessions by Project Names: Displays the total count of sessions for each project.
Values displayed:
-
Project Names
-
Total Number of Sessions
-
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: Filter sessions based on specific weekdays.
-
Feature Name: Filter sessions by specific licensed features.
-
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: Filter sessions by specific users.
-
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.
-
Group Name: Filter sessions by groups.
-
Project Name: Filter sessions by projects.
Interpreting this report
- Session counts measure demand events, not workload. One thousand 10-minute sessions and 10 hundred-hour sessions 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 idle hoarding. Read this report against the hours in Feature usage per group.
- By-user session counts expose behaviour: 1 user with an order of magnitude more sessions than peers is either scripting license checkouts or fighting an unstable application - both worth knowing.
- The group and project charts attribute session volume the same way the usage reports attribute hours, so a project heavy here but light in usage hours runs many brief sessions - typical of validation or batch workflows.