Skip to main content
Announcements
Global Transformation Awards! Applications are now open. Submit Entry
cancel
Showing results for 
Search instead for 
Did you mean: 
yosuke-coupa
Partner - Contributor III
Partner - Contributor III

Clarification on Tenant Deletion and Entitlement Consumption

I am looking for clarification on the behavior of deleting a tenant and its effect on entitlement consumption.  The relevant Qlik Developer documentation states:

Deleting a tenant will not deallocate user-based entitlements assigned on that tenant - you should do this activity using the licenses API. Any entitlements consumed in the month, such as Application Automation runs, will still be counted in your overall monthly consumption.

I understand that the deletion request will put the tenant in a "disabled" state, and all of its data will be completely purged after the specified time frame, defaulted to 30 days.  If the tenant is purged, will the entitlement not be deallocated?  If it's not deallocated, how would you be able to make a request to the licenses API to a purged tenant?

Labels (2)
1 Solution

Accepted Solutions
DaveChannon
Employee
Employee

With respect to user entitlements (e.g. assigned professional or analyzer entitlements), these are stored at the license level (not the tenant level) against the user's subject. As such, you can call the license API on any tenant attached to that license to deallocate users.

The historical reason for this was that we wished to provide you a single "account" against which you could draw down licenses, while also allowing you to have some users - such as your admin accounts - which could exist on many tenants but only consume 1 license.

To give you a preview of the future, next year we aim to support full isolation of a license assignment at a tenant level (i.e. stopping this shared concept and making it possible to clear tenant entitlements, as you will be able to assign a set amount of entitlement to each tenant you create).

View solution in original post

3 Replies
DaveChannon
Employee
Employee

With respect to user entitlements (e.g. assigned professional or analyzer entitlements), these are stored at the license level (not the tenant level) against the user's subject. As such, you can call the license API on any tenant attached to that license to deallocate users.

The historical reason for this was that we wished to provide you a single "account" against which you could draw down licenses, while also allowing you to have some users - such as your admin accounts - which could exist on many tenants but only consume 1 license.

To give you a preview of the future, next year we aim to support full isolation of a license assignment at a tenant level (i.e. stopping this shared concept and making it possible to clear tenant entitlements, as you will be able to assign a set amount of entitlement to each tenant you create).

yosuke-coupa
Partner - Contributor III
Partner - Contributor III
Author

@DaveChannon That makes sense, thanks for the clarification.

I have a follow up question. When the mechanism to clear tenant entitlements upon tenant deletion is implemented, what will happen to the accounts that exists across more than one tenant (e.g. as you mentioned, admin accounts)?  Would deleting a tenant release licenses only if the account doesn't exist in other active tenants?  Or are you saying that the entire entitlement assignment logic is changing where you allocate a set amount of entitlement to a tenant, removing the concept of an account that can exist in multiple tenants?

DaveChannon
Employee
Employee

The latter @yosuke-coupa, and we'll try to simplify the enforcement logic at the same time.