Grant licenses to an organization
You can grant licenses to an organization in the organization’s entitlements in 10Duke SysAdmin.
You grant licenses using a product package, and a separate license is created for every licensed item in the package. You define a validity time and credit that applies to all the licenses granted, but you can change these later per license if needed.
Limitations:
-
The credit type you can use for a license depends on the license model. For example, to use seat credit, the license model must have settings in place that restrict license use based on seats.
-
We recommend that you only use one type of credit for licenses that you have granted using the same product package.
You can change the credit type per license after granting them in SysAdmin, and the Entitlement Management REST API allows you to use different types of credit already when granting licenses, but we don’t recommend this.
See also how to add credit to existing licenses.
Before you start:
-
Make sure the organization has an entitlement where you want to place the licenses.
-
Make sure your product package is ready for granting licenses:
-
It contains all the licensed items that you want to grant licenses to.
-
It’s associated with the license model you want to use for the licenses.
-
It’s active and valid.
-
To grant licenses to an organization:
-
In the left sidebar, go to ENTITLEMENTS > Organization.
-
Click Change organization, search and select the organization, and click Confirm.
The organization’s entitlements table opens.
-
Select the entitlement where you want to place the licenses.
-
On the Licenses tab, select Actions > Grant licenses. A dialog opens.
-
In Product, select the product package that contains the licensed items you want to grant licenses to.
Note: If you grant a new license with a custom license model and the entitlement already has a license for the same licensed item, the license model may define that the existing license is updated instead of creating a new license.
In this case, the existing license is updated based on the product package, and the new credit is added to the earlier credit. Make sure you define the same validity time that the existing license has, or granting the license fails.
With an out-of-the-box floating license model, a new license is always created.
-
Define the license validity:
-
Valid from: Define the start date from which the license is valid. Use the format YYYY-MM-DD.
-
Valid until (optional): Define the end date after which the license is no longer valid. Use the format YYYY-MM-DD.
-
-
Define one type of credit for the license:
-
Seat count: Define the number of seats the license has.
You can define seat credit if the license uses either the out-of-the-box floating license model or a custom license model that defines a seat count constraint.
-
Use count: Define the maximum quantity of usage that the license allows.
The client application can specify the quantity to be consumed from the credit in the license consumption request; otherwise 1 unit is consumed from the credit per request.
You can define use count credit if the license uses a custom license model that defines a use count constraint.
-
Use time: Define the maximum use time that the license allows. The end users’ total cumulative use time cannot exceed this amount.
Select the time unit (seconds, hours, or days) and enter the amount of time allowed. When the license is being consumed, the time consumption is calculated in milliseconds.
You can define use time credit if the license uses a custom license model that defines a use time constraint.
Note: If the licensed item’s advanced settings in the product package define a credit multiplier, that is used to calculate the final credit granted in the license.
-
-
Click Save to grant the licenses.
Next steps:
-
Authorize user groups and device groups to consume the licenses.
-
If you need to, for example, change the validity or credit of some of the licenses, edit the licenses.