Individual License Usage

Individual License Usage is used to load monthly user-level license usage data.

Use this page when you need Yarken to track which users are associated with specific product licenses for a reporting period. This data supports user-level license reporting, license reclaim analysis, SaaS governance, TBM allocation, mapping, and software license intelligence.

Individual License Usage sits under Yarken Designer > Consumption > Individual License.

What Individual License Usage helps you do

Use Individual License Usage to:

• Load monthly user-level license usage data

• Track license consumption by user and product

• Associate license usage data with a vendor

• Support individual license review and reclaim decisions

• Compare license assignment with product activity where available

• Feed License Usage analytics and Software License Intelligence

• Provide usage inputs for TBM allocation and mapping

Individual-level license data helps teams move from product-level capacity to user-level accountability.

When to use Individual License Usage

Use Individual License Usage when the data identifies license usage at the user level.

Typical examples include:

• Product licenses associated with a user email

• User-level license assignment or consumption records

• Product SKU usage by user

• Monthly license snapshots by user

• User-level license counts for reporting

Use Tenant License Usage when the data summarizes total, consumed, and available licenses at tenant or product level.

Use Product Usage when the data describes product or application activity.

How Individual License Usage fits the consumption model

Individual License Usage is part of the broader Consumption area in Yarken Designer.

The typical flow is:

1. Select the reporting year

2. Open Consumption > Individual License

3. Upload individual license usage for the relevant month

4. Review the upload in Uploaded Files

5. Check any errors or mapping issues

6. Use upload rules where transformation is required

7. Review the data in License Usage analytics and related reporting

The uploaded data becomes available for downstream reporting once the file is loaded and processed successfully.

Page layout

Individual License Usage includes three tabs.

Use Overview for month-based upload activity. Use Uploaded Files when checking what has already been loaded.

Overview tab

The Overview tab shows the selected year as monthly upload tiles.

Each month represents a reporting period. Use the relevant month tile to upload the individual license usage file for that month.

Before uploading, confirm that:

• The selected year is correct

• The file represents the month you are uploading into

• The report date in the file matches the selected month and year

• Tenant identifiers already exist in Yarken where required

• User email values are consistent and valid

• Product names and SKU values match the expected source structure

This helps avoid failed uploads and improves reporting accuracy.

Uploaded Files tab

The Uploaded Files tab shows the files that have been loaded for Individual License Usage.

Common columns include:

Use this tab to confirm whether a file loaded correctly and whether the expected number of records was processed.

Uploaded file actions

Each uploaded file can include file-level actions.

Common actions include:

Use Re-map and reload when the field mapping needs correction before the file is processed again.

Upload Rules tab

The Upload Rules tab lets administrators create rules that transform data during upload.

Upload rules are useful when source files need controlled cleanup or standardization before the data is loaded.

Rules can help with tasks such as:

• Assigning default values

• Standardizing field values

• Updating target fields during upload

• Supporting consistent mapping across recurring files

Use upload rules carefully. They affect how uploaded data is transformed and can change downstream reporting results.

Required data checks

Before uploading individual license usage data, confirm these checks.

Strong source data improves user-level license reporting quality.

Relationship with License Usage analytics

Individual License Usage feeds user-level reporting in the License Usage analytics cube.

In Analytics, individual license data can help teams review:

• Report Date

• Product Name

• Product SKU ID

• User Email

• Count

• Tenant dimensions

• Vendor context

Use Analytics to compare user-level license consumption across products, tenants, vendors, and reporting periods.

Relationship with Software License Intelligence

Individual License Usage supports software license intelligence by providing the user-level view of license allocation and consumption.

This helps teams:

• Identify users associated with specific products

• Review license assignment at user level

• Compare assignment with product activity where available

• Support reclaim and reassignment decisions

• Improve SaaS governance and renewal planning

Individual-level data is most useful when reviewed alongside tenant license capacity and product usage activity.

Relationship with Multi Cube

Individual License Usage can be combined with other data in Multi Cube when matching fields are available.

Example use cases include:

• Linking user email to employee data

• Connecting user-level license records to application or asset records

• Comparing assigned licenses with activity or spend

• Supporting license review by team, cost center, or entity

Use Multi Cube when the question needs user-level license data combined with another cube or master data source.

Recommended practices

Use these practices when managing Individual License Usage:

• Load files consistently for each reporting month

• Confirm the selected year and month before uploading

• Keep user email values consistent across files

• Keep product and SKU values consistent across months

• Review uploaded file status after each load

• Check loaded records against the expected record count

• Resolve errors before using the data in reporting

• Use upload rules only when the transformation is required and repeatable

• Review individual usage with tenant capacity and product activity where available

Consistent user-level uploads improve license governance and reclaim analysis.

Common issues

If an individual license usage file does not load correctly, check:

• Whether the Tenant ID exists in Yarken

• Whether the report date matches the selected upload month and year

• Whether required fields are populated

• Whether user email values are valid and consistent

• Whether product or SKU values are formatted consistently

• Whether the file has duplicate or incomplete records

• Whether the uploaded file mapping is correct

• Whether upload rules changed the expected field values

• Whether the file status shows an error in Uploaded Files

If results look incorrect in Analytics, start by checking the uploaded file status, record count, user email values, and reporting period.

Next step

• Product Usage

Related content

• Consumption

• License Usage

• Software License Intelligence

• Tenant License Usage

• Monthly License Usage

• Yarken Designer