All pages
Powered by GitBook
1 of 1

Disabling Entitlements

At the entitlement level, it's ideal for a single customer, or group of customers, or a single instance of a Local License server at a site vs switching off everything on a particular customer.

This is very useful for end users who are delinquent or refuse to pay for their license or any other reason you need to block access to your software.

You can now “switch off” entitlements with one click.

Disabling an entitlement

As you can see above, the status is set to "disabled" with a red icon, and the button in the top right has changed color and is set to "Enable entitlement," ready for you to reverse the process when required.

The entitlement "disabled" status can also be seen in the list of all your entitlements.

Re-enable a disabled entitlement.

The status will now show as "created" where it was before it was changed. The red disable button shows again for any future changes.

The entitlement is now fully activated again, and the activation codes attached will function again.

Note: Entitlements can be disabled independently of the customer being disabled, which means that you can disable one or the other, but the entitlement will remain disabled if you set it here, even if the customer is re-enabled, etc., i.e., if you disable an entitlement, you have to re-enable it directly not via the customer process.

For entitlements to be disabled in the field, the best practice is to set your software to call back to Zentitle once a day and refresh the license on the application start or run. This way, when a license/entitlement/activation code is checked against its rights at Zentitle, it will show as disabled. Then (assuming you set up your code this way), it will prevent access to your software until you re-enable the entitlement.

Using API calls to disable entitlements: