The Entitlements section in the License Management workspace shows all operational license entitlements currently stored in Raynet One. An entitlement defines what is licensed for a product, including the license model, metric, quantity, and validity period. This data is used for allocation, reconciliation, ELP calculation, and compliance reporting.
Entitlements are usually generated from license contracts. The contract is the commercial source, while the entitlement is the operational object used by license management processes. Incomplete or incorrect entitlement data can make allocation results, ELP values, and compliance evaluations unreliable.
License model and License metric are especially critical. They determine entitlement identity, generation, linking, and processing. Changing these values may affect existing assignments and downstream compliance results.
Creating entitlements
In Raynet One, entitlements can be created manually or generated automatically from license contracts. In the standard workflow, contract-driven entitlement creation is the preferred approach because it preserves source traceability and supports consistent lifecycle processing.
Manual entitlement creation should only be used if no corresponding license contract exists in the system.
Contract-driven entitlement creation
When a license contract is created and its product data is saved, Raynet One automatically generates the corresponding entitlement. The fields License model and License metric are mandatory for correct entitlement generation and assignment. Together, these values help determine which entitlement is created or linked.
Depending on the purchased license rights and the applicable product terms, Raynet One may create or link separate Perpetual and Maintenance entitlements. The selected license model must reflect the rights documented in the corresponding license contract.
Some products require a dedicated Maintenance entitlement, while for others a Perpetual entitlement is sufficient.
|
Be aware: |
Entitlement lifecycle and automatic events
Contract and entitlement data is used to generate lifecycle events automatically. The values defined for License start and License end determine when an entitlement becomes valid, when its validity
ends, and which related events appear in the Calendar.
License start
When an entitlement is linked and License start is defined, Raynet One creates a purchase-related event. For the first purchase of an entitlement, the system creates a Purchased Event.
If an additional purchase is recorded for the same entitlement later, the system creates a Purchased Renewal instead. This behavior applies to both contract processing and entitlement lifecycle tracking.
License end
The License end date defines the end of the entitlement validity period. It is also used for expiration-related event handling, including:
•License Expiration Warning
•License End Event
On the last valid day, the final expiration state is reached. After the defined end date, the entitlement is no longer considered valid for further license coverage.
|
Be aware: |
 |
Best practice: |
Accessing entitlements
Access via Workspaces > License Management > Entitlements.
In the Entitlements tab, you can view all entitlement records in a single list. Each row shows the attributes that are relevant for license availability and compliance: product, name, license model, license metric, quantity, allocated quantity, remaining quantity, validity dates, and other values used for compliance processing.
The following figure shows the Entitlements tab with the entitlement list and the available toolbar actions.
The Entitlements tab displays entitlement records in a list. Each row represents one entitlement. The following columns describe the visible entitlement data:
COLUMN |
DESCRIPTION |
|---|---|
Products |
Product associated with the entitlement. A vendor icon is displayed if available. Products are typically created and maintained through license contracts. |
Name |
Display name of the entitlement record. |
Model |
License model assigned to the entitlement, for example, Perpetual, Subscription, or Maintenance. The selected model is part of the entitlement definition and influences entitlement assignment. |
Metric |
License metric used for counting, for example Core-based, Device-based, or User-based. Together with the license model, the metric determines how the entitlement is identified and processed. |
Quantity |
Total licensed quantity stored for the entitlement. |
Allocated |
Quantity currently assigned to resource groups. These licenses will only be used for devices that are inside of these resource groups. |
Remaining |
Unallocated quantity, meaning quantity that is not assigned to any resource groups. The Remaining value is calculated from Quantity minus Allocated and can be used for open demand in the system. |
License start |
Start date of the entitlement validity period. |
Maintenance quantity |
The quantity covered by an active maintenance or Software Assurance entitlement. For subscription licenses, this equals the license quantity. For Perpetual licenses, this reflects the quantity of the linked Maintenance entitlement. |
Activation |
Date on which the entitlement became active in the system. |
Expiration |
End date of the entitlement validity period. If no expiration date is defined, the entitlement is treated as non-expiring in the record. |
Last demand synchronization |
Timestamp of the most recent synchronization with license demand data. |
Managed by |
Responsible owner or managing system for the entitlement record. |
The Entitlements overview toolbar provides the following actions:
ACTION |
DESCRIPTION |
|---|---|
Refresh |
Reloads the list using the latest available data. |
Add |
Creates a new entitlement record manually. |
Edit |
Modifies the selected entitlement. |
Remove |
Deletes the selected entitlement. |
Filter |
Filter for required items. |
Export |
Export the Entitlements view. |
Search |
Filters the list using a text search. |
The Ungoverned tab lists commercial software products discovered in your environment that have no corresponding license contract or entitlement yet. From here you can directly create entitlements for these products to bring them under governance. The list shows product name, edition, vendor, and number of installations. Expand a row to view version details.
Ungoverned tab showing detected products that can be converted into entitlements.
Create an entitlement from an ungoverned product
To create an entitlement from an ungoverned product:
1.Open the Ungoverned tab.
2.Select the product from the list.
3.Click Add in the toolbar.
4.In Product details, verify the prefilled Name and Vendor values.
5.Complete or verify the remaining license information: Version, Edition, License model, and License metric.
6.Click Next.
7.In Summary, review the selected product and license information.
8.Click Create to proceed, or Back to return to the previous step.
9.Wait while the request is processed in Progress.
10.In Finished, confirm that the entitlement has been created and click Finish.
The new entitlement is then available in the Entitlements overview and can be used for license management processes such as allocation, reconciliation, and compliance calculation.
Edit and allocate entitlements
After an entitlement has been created or generated, you can edit it in the Entitlements section to maintain license allocation and responsibility settings.
Allocating licenses defines how the entitlement quantity is assigned to operational scopes such as resource groups and responsible teams. This makes the allocated and remaining quantities visible and turns the entitlement from a stored license right into an actively managed assignment.
|
Note: A resource group must already exist in Configuration > Resource groups before it can be selected in the License allocation step. |
Allocate licenses to an entitlement
To allocate licenses for an existing entitlement:
1.Open the entitlement.
2.Click Edit.
3.In License allocation, select the resource group.
4.Assign the user group.
5.Enter the number of licenses to allocate.
6.If required, click + Add to add another license allocation.
7.Click Next to continue to Responsibility.
8.Select the user group that should be responsible for the entitlement.
9.Click Next to continue to Summary.
10.Review the selected license allocation and responsibility.
11.Continue through Progress while the system applies the change.
12.In Finished, confirm that the entitlement has been updated and click Finish.
When + Add is unavailable
If + Add is unavailable in the License allocation step, one of the following conditions applies:
CONDITION |
MEANING |
|---|---|
No licenses remaining |
All available licenses have been allocated. No further allocations can be added until the total quantity is increased or an existing allocation is reduced. |
All resource groups allocated |
All resource groups in the environment have already been added as allocations to this entitlement. |
Result after allocation update
After the wizard is completed, the entitlement record shows the updated allocation and responsibility data in the Details tab. For example, the Details tab can show you how many licenses are allocated, how many licenses remain available, and which user group is responsible for the entitlement.
Below Price information, additional sections such as License timeline, License allocations, and License contracts provide further entitlement context. The License timeline section shows the recorded lifecycle events of the entitlement over time.
What you can verify here
From the Entitlements section, you can verify:
•Which products are covered by which active entitlements.
•Which license model and metric apply to each entitlement.
•Stored quantity vs. allocated vs. remaining quantity.
•When the entitlement starts and expires.
•Which resource groups and user groups are assigned to the entitlement.
This makes the Entitlements section relevant for operational validation and for troubleshooting incorrect compliance results.
|
Best practice: |