Feature usage per user
To see which features each user uses, open the Feature usage per user report. Use it to identify key users and understand feature adoption.
The following screenshot shows the stacked bar chart and table of feature usage by user:
The Feature usage per user report breaks down feature usage by individual user.
Visualizations
The report has the following visualizations:
- Chart: A horizontal stacked bar chart of Usage Time (Hours) by User Name. Each colored segment is one feature, so the bar shows a user's total and the split across features. QuickSight labels the visual Chart. Values displayed:
- User Name
- Usage Time (Hours)
- Table: Use this table to compare how each user works with different features over the selected time range. It shows usage time (hours) alongside the username, feature, server, and vendor, ordered by usage time. QuickSight labels the visual Table. Values displayed:
- User Name
- Feature Name
- Server Name
- Vendor
- Usage Time (Hours)
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. - Server Name: Select any server name.
- Vendor: Select any vendor.
- License Type: Select any license type.
- Additional Key: Select any additional key.
- Feature Name: Select any feature name.
- 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 any username.
- 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 any group name.
- Project Name: Select any project name.
- Product Name: Select any product name.
- Version: Select any version.
- Country: Select any user country.
- Region: Select any user region.
- Department: Select any department.
Interpreting this report
Use these points to read the report:
- The stacked bar per user is a workload profile: its length ranks the user's total hours, and its segments show which features consume that time. Users whose bar a single feature dominates are single-tool specialists. Broad bars mark workflows that span several tools, which named licensing serves poorly.
- The power users this chart identifies are the people to consult before pool changes, not the people to reclaim licenses from. The ranking is total hours, so it shows dependency, not inefficiency. For inefficiency, compare against idle time in License activity.
- A user consuming hours in a feature their team does not otherwise use is a data point for license-tier and training decisions. It can also explain a saturated pool nobody else recognizes.
The documentation team might draft this page using a large language model. A technical writer reviews every page and verifies it against the product before publishing it. A human makes the final decision.