Skip to main content Skip to complementary content

Qlik Sense licenses

Qlik Sense Enterprise is the server version of Qlik Sense that you can deploy on a single node, or on multiple nodes. Qlik Sense Enterprise licenses are based either on access types, or on tokens.

For detailed information on Qlik Sense licensing options, see Qlik's legal terms, product terms, and Licensing Service Reference Guide:

Unified license

You can use a unified license in multiple deployments. A unified license shares the same signed key between:

  • multiple Qlik Sense Enterprise deployments
  • multiple QlikView Server deployments
  • QlikView Server and Qlik Sense Enterprise deployments

Applying the same signed key to multiple deployments lets you share the same users and access types. Users can access all connected deployments using the same Professional or Analyzer access allocation.

Qlik Sense Enterprise

A Qlik Sense Enterprise deployment can be licensed using two different models: the serial and control number and the signed license key. The License Enabler File (LEF) defines the terms of your license and the access types that you can allocate to users. Your Qlik Sense Enterprise license is based either on access types, or on tokens. A core-based license is also available.

With a signed license key, you need internet access (direct or through a proxy) to access the cloud-based license backend, for user assignments, analytic time consumption, and product activations.

User-based and capacity-based licenses

A user-based license grants a predefined number of access allocations that can be assigned to unique and identified users. In Qlik Sense Enterprise, user-based licenses are either Professional and Analyzer Users licenses, or User access passes allocated with a Token license.

A capacity-based license grants a predefined number of time allocations for accessing Qlik Sense Enterprise that can be used by identified or anonymous users. In Qlik Sense, capacity-based licenses are either based on Analyzer Capacity access, or Login access pass allocated with a Token license.

Access types

Access types licenses are the Professional and Analyzer Users licenses (user-based) and Analyzer Capacity licenses (capacity-based). You can combine these for a subscription based license if you use the signed license key when your deployment is activated. You can combine only user-based licenses if you are using a perpetual license.

Information noteAfter changing to a license with a signed key, you cannot return to using the old serial and control number license model.

Professional and Analyzer Users license

A Professional and Analyzer Users license is composed of Professional and Analyzer access types.

  • Professional access (user-based) is allocated to an identified user to allow the user to access streams and apps within a Qlik Sense site. The professional access is intended for users who need access to all features in a Qlik Sense installation. A user with professional access can create, edit, and publish sheets or apps, and make full use of the available features, including administration of a Qlik Sense site.
  • Analyzer access is allocated to an identified user to allow the user to access streams and apps in the hub. The analyzer access is intended for users who consume sheets and apps created by others. A user with analyzer access cannot create, edit, or publish sheets or apps, but can create and publish stories, bookmarks and snapshots based on data in apps. The user can also print objects, and export data from an object to Excel.

Analyzer Capacity license

An Analyzer Capacity license is composed of Analyzer Capacity access type.

Analyzer capacity is a consumption-based license type, which is like analyzer access regarding available features. Users can access streams and apps in the hub and consume sheets and apps created by others. Analyzer capacity access allows users to create stories, bookmarks, and snapshots based on data in apps. Creating, editing, or publishing sheets or apps is not possible.

With an analyzer capacity license, you subscribe to analyzer time, a defined number of minutes per month (calendar date). These minutes are shared between users and can be consumed by anyone who is part of the user group, including anonymous users. Consumption is measured in units of six minutes. For each new six-minute period, a unit is consumed.


You use tokens to allocate access passes to users so that they can access Qlik Sense. The License Enabler File (LEF) determines the number of tokens that you can allocate to different access passes. A user without an access pass cannot access apps.

Information noteThe token license is available only to customers with existing Qlik Sense Token licenses.

There are two types of access passes that can be allocated using tokens:

  • User access pass (user-based) is assigned to unique and identified users allowing them unlimited access to apps, streams, and other resources.

  • Login access pass (capacity-based) allocates a block of passes to a group for infrequent or anonymous access. Allows full access for a limited period.

When you allocate tokens, the number of available tokens is reduced. Each access type costs a certain number of tokens, and if the token balance is zero or insufficient, you cannot allocate more to the access types. You can free up tokens and choose to use the tokens differently. The number of tokens for the Qlik Sense site can be increased or decreased by activating a new license.

For more information on access passes and the token consumption model, see Managing licenses.

Core-based site

Qlik Sense Enterprise core-based sites are licensed based on the number of CPU cores on which the software will operate. The license is administered using a License Enabler File (LEF), which limits the maximum number of cores on which the Qlik associative engine and its components may operate. A Core means a single processing unit within a processor or CPU, whether physical or virtual, including a vCPU or virtual core, which can execute a single software thread at a time.

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 – let us know how we can improve!