Home > Licensing > Review entitlement consumption

Review entitlement consumption

Cadence: Weekly

Subscription model: User-based only (Qlik Sense Enterprise SaaS, Qlik Sense Business)

Roles: Tenant Admin (TA)

Last verified: 2026-09

Benefits:

• Confirms Professional / Analyzer headroom before new users are added
• Identifies inactive Professionals who could be downgraded to Analyzer
• Forecasts entitlement consumption ahead of renewal

Goal

User-based subscriptions divide users into Professional (creators) and Analyzer (consumers); entitlements affect both UI access and what built-in roles are auto-assigned. Weekly review keeps headroom visible and surfaces inactive Professional users who could be downgraded.

Note. This activity does not apply to capacity-based subscriptions. As of February 2, 2026, capacity-based tenants no longer have the Basic User construct—every authenticating user is deducted from total user capacity purchased, with capabilities controlled by access control alone. Qlik's own docs have since dropped the Full User label entirely in favor of generic User—this playbook still uses Full User below for continuity with the Feb 2026 transition, but don't expect to find that exact term in current Qlik UI/docs. See About this playbook → Subscription model.

Tasks

If you ALSO operate a capacity-based tenant—capacity-based assignment gotchas

Subscription-model boundary. Everything above this line is user-based only. Everything below this line is capacity-based only and is included here as a cross-reference for admins who operate both models. If you only operate a user-based tenant, stop reading here.

• Every authenticated user consumes a user-capacity slot. Since the Basic User tier was removed (February 2, 2026) there is no restricted-view tier—any user who can authenticate to the tenant counts against purchased user capacity. Audit IdP group membership, space membership, and who can reach the tenant before capacity bites, not after.
• Manual de-allocation reverts on next login while dynamic license assignment is on. To hard-remove a user's assignment, use qlik-cli or PATCH /api/v1/users/{id} and freeze auto-assign for that user.
• Multi-tenant subscriptions pool user entitlement across tenants. Orphan users surfaced from a sibling tenant (for example, via inconsistent IdP / OAuth setup) can consume slots from the shared pool and lock everyone out—review unexpected user records for tenantId mismatches. (community thread on orphan-user lockouts)
• The Collaboration Platform User role does NOT consume a user-capacity slot. It is the supported path to grant Microsoft Teams chatbot integration to a user who doesn't otherwise authenticate to the tenant, without burning capacity. This exception was documented before the Feb 2026 Basic/Full consolidation (back when it was framed as doesn't promote Basic to Full)—Qlik hasn't republished it under the new model, so treat the underlying behavior as likely still true but unconfirmed post-change, and verify directly with Qlik if this matters for a capacity-constrained tenant.
• The Entitlements toggles in tenant settings were removed on February 2, 2026. Auto-license assignment now lives on Manage users → Permissions; pre-migrate any provisioning logic that assumed the old toggles.

Automation helpers

• Qlik Cloud Monitoring Apps Deployer—Installs / maintains the Entitlement Analyzer cited above.

References

• Managing user entitlements
• Qlik Cloud user-based subscriptions
• Streamlining user types in Qlik Cloud capacity-based subscriptions
• Entitlement Analyzer (Tooling appendix)
• Collaboration Platform User role exception (community)
• Unable to remove or de-allocate user license—license is sticky (community)

Tags: #weekly #licensing #entitlement #user_based #entitlement_analyzer