Feature usage per group

To see which features each user group uses, open the Feature usage per group report. Use it to analyze group-level feature consumption.

The following screenshot shows the bar chart and table of feature usage by group:

The Feature usage per group report breaks down feature usage by user group.

Visualizations

The report has the following visualizations:

• Chart: A bar chart of Usage Time (Hours) by Feature Name, with the user group shown in the legend. QuickSight labels the visual Chart. Values displayed:
  • Feature Name
  • Usage Time (Hours)
• Table: Use this table to compare how each group uses features over the selected time range. It shows usage time (hours) alongside the group, feature, server, and vendor, ordered by usage time. QuickSight labels the visual Table. Values displayed:
  • Group 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:

• This is demand accounting by team, and the place chargeback conversations start. Version 26's group-usage reporting was used to implement license chargeback (usage billing), and the hours in the table serve the same purpose here.
• The stacked bars show each feature's demand mix. A feature consumed by one group is that group's cost to justify. A feature that spreads evenly across groups is shared infrastructure. This distinction matters when a saturated pool needs a budget owner.
• Usage hours here include idle time within sessions. For efficiency-adjusted numbers per group, use License activity grouped by group, which splits actual from idle time.
• The group totals only add up meaningfully if your directory synchronization assigns every user to a group. Unattributed usage disappears from this view rather than appearing as "unknown".