Skip to main content Skip to complementary content

Home > Licensing > Subscription review

Subscription review

Last updated: 2026-11-03

Cadence: Yearly

Subscription model: All

Roles: Service Account Owner (SAO), Tenant Admin (TA—for IdP item only)

Last verified: 2026-05

Initial Recurring
Estimated time 2 hr 1 hr

Benefits:

  • Aligns next-year capacity plan with actual prior-year consumption
  • Surfaces add-ons that are no longer being used
  • Confirms tenant region(s) still match data-residency obligations

Goal

The SAO is the documented role for managing the subscription in My Qlik per Qlik's SAO / Tenant Admin FAQ. Tenant Admins can see the subscription type from the admin console, but only the SAO has My Qlik subscription-management rights. The annual review covers pricing plan, tier, capacity, add-ons, region, and reconciles actual consumption (including overage) with the contracted entitlement. Capacity-based Qlik Cloud Analytics has four tiers—Starter, Standard, Premium, Enterprise—and user-based subscriptions include Qlik Sense Enterprise SaaS and Qlik Sense Business.

Note on contract term. Reducing tier, capacity, or add-ons mid-term is generally not possible on a multi-year contract—most downsizing decisions can only be actioned at renewal. If the subscription is a multi-year contract, treat the surface unused add-ons items below as renewal-planning inputs rather than actions to take immediately, and time the review to feed the renewal cycle. For multi-tenant subscriptions, entitlement is pooled across tenants—see Subscription and entitlement sharing.

Tasks

Task TA AA DA AuA SAO
Review pricing plan, tier, capacities, add-ons (Qlik Answers, Qlik Predict, large-app support) ✓
Confirm tenant region and any plans to move regions (region moves require a Qlik Support case) ✓
Reconcile annual capacity / overage history with billing ✓
Confirm that all tenants under the same license use the same IdP to prevent duplicated entitlement assignments ✓ ✓

References

Tags: #yearly #licensing #subscription #sao

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!