LICENSES

After creating a product edition, you can create licenses based on that edition.

The selected edition determines which license properties are available and which values can be changed during license creation. Therefore, the edition has a direct impact on how the license can be configured.

CUSTOMER AND EDITION

A license is always assigned to a customer and an edition. A license can be transferred from one customer to another.

You can also change the edition of a license, but only if the new edition has the same core edition properties, meaning the same provisioning mode and client type.

LICENSE TYPE

License types can be used to categorize licenses and act as filters in many SLASCONE views.

License types are configured in the administration area. For more information, see Custom Types, Lists and Tags.

LEGACY KEY

When creating a license, you can specify a legacy license key. This allows you to map the new SLASCONE license to a license from a previous licensing system.

This is especially useful during migration scenarios. For more information, see Migrating from Legacy Licensing Systems.

LICENSE PROPERTIES

Depending on the edition's adjustable properties, you may be able to change the values of features, limitations, variables, and constrained variables during license creation.

FEATURES

Features are used to enable or disable specific functionality for the license. If a feature is adjustable in the edition, the license creator can change its value during license creation.

CUSTOM RULES FOR FEATURES

Custom rules allow you to define a custom expiration date for a specific feature. This makes it possible to:

• Temporarily enable a feature, for example for one month, without creating a new license.

• Define a different expiration date for individual features.

Custom rules are deactivated by default and must be explicitly enabled at the product level.

LIMITATIONS

Limitations, or quotas, are numeric values used to restrict the scale of usage. Typical examples include the maximum number of users, devices, jobs, or other measurable units.

Limitations can be interpreted by the client application either statically or in consumption-based mode.

VARIABLES

Variables are generic fields used to store additional license information. They are useful when a value should be part of the license but cannot be represented naturally as a feature or limitation.

A variable can also be marked as required in the edition. In that case, a value must be provided when creating the license.

CONSTRAINED VARIABLES

Constrained variables are variables with predefined values. These values are populated from a custom list.

TOKENS

For device-based licensing, you need to define the number of tokens available for the license.

For more information, see Token Keys.

LICENSE VALIDITY

License validity settings vary depending on the selected edition and its expiration type.

START DATE

The start date can only be set for a new license or for an existing license where the configured start date has not yet been reached.

The start date determines when a license becomes valid. The Active status of a license is independent of the start date. This means a license can be active even if it only becomes valid at a later date.

For more information, see Start Date - Client/API Considerations.

EXPIRATION DATE

Depending on the edition, the expiration date can be configured in different ways:

• Custom Date: the license expires on a specific date and time
• Subscription / Perpetual: use this setting if the license has no fixed expiration date
• Days after activation: the expiration date is calculated dynamically based on the activation date or, if applicable, the configured start date

MAIL LOG

Each license contains a log of sent alerts. Alerts are configured as an edition property, not as a product property.

AUDIT LOG

The audit log records license changes and provides traceability. For more information, see Audit Log.

MANAGING USERS OF A NAMED USER LICENSE

Named user licenses allow you to create, edit, and delete users assigned to the license.

For more information, see Named User Licenses.

CLONE LICENSES

A license can be cloned from the license list. Cloning creates a new license based on the selected source license.

Please note:

• License tags are not copied.

• Users and user groups are not copied.

• Assignments are not copied. They are created according to the provisioning mode and license activation behavior, just like with a new license.