Access passes

There are two major license types: one that is user-based and one that is token-based.

  • User-based license: you can allocate professional access and analyzer access. The LEF determines the distribution of the two access types.
  • Token-based license: you can allocate user access and login access. The LEF determines the number of tokens that you can allocate to the two access types.

In addition to these two types there is the analyzer capacity license that is similar to analyzer access regarding available features, but where consumption is time based (analyzer time).

User-based licenses

User-based licenses grant a predefined number of professional and analyzer access allocations. The distribution of the access types is determined by the LEF.

The following table lists the available access types for a user-based Qlik Sense license.

Access type Description
Professional access

You allocate professional access 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.

There is a direct relationship between the access type (professional access) and the user. If you deallocate professional access from a user, the access type is put in quarantine, if it has been used within the last seven days. If it has not been used within the last seven days, the professional access is released immediately. You can reinstate quarantined professional access, to the same user, within seven days.

The maximum number of parallel user connections for a single user of this type of access pass is five (5). When a user with the maximum number of parallel user connections ends a connection (for example, by logging out) five minutes must pass before the user can use the access pass to add another connection (for example, by logging in).

Analyzer access

You allocate analyzer access 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 create bookmarks, print objects, stories, and sheets, and export data from an object to Excel.

There is a direct relationship between the access type (analyzer access) and the user. If you deallocate analyzer access from a user, the access type is put in quarantine, given that it has been used within the last seven days. If it has not been used within the last seven days, the analyzer access is released immediately. You can reinstate quarantined analyzer access, to the same user, within seven days.

The maximum number of parallel user connections for a single user of this type of access pass is five (5). When a user with the maximum number of parallel user connections ends a connection (for example, by logging out) five minutes must pass before the user can use the access pass to add another connection (for example, by logging in).

Analyzer capacity

Analyzer capacity is a consumption-based license type that is similar to analyzer access regarding available features. Analyzer capacity is available to any users, including anonymous users, and they share the monthly analyzer time allotment, which is consumed in units of six minutes.

Token-based licenses

The following table lists the available access types for a token-based Qlik Sense license.

Access type Description

User access pass

This type of access pass allows a unique and identified user to access the hub.

The access pass is valid within an entire Qlik Sense site. For example, if a user first connects to a node in the USA and then, at a later stage, connects to a node in the UK, the user consumes the same access pass, if the two nodes are connected to the same central node.

See: Architecture

The maximum number of parallel user connections for a single user of this type of access pass is five (5).When a user with the maximum number of parallel user connections ends a connection (for example, by logging out) five minutes must pass before the user can use the access pass to add another connection (for example, by logging in).

One (1) token corresponds to one (1) access pass. The access passes are allocated using the Qlik Management Console (QMC).

Login access pass

This type of access pass allows an identified or anonymous user to access the hub for a maximum of 60 continuous minutes per 28-day period. If the user exceeds the 60 minutes time limitation, the user connection does not time out. Instead, another login access pass is used. If no more login access passes are available, the user connection is discontinued.

  • If an identified user is disconnected, the user can re-connect and continue to use the same access pass, if re-connecting within the 60 minutes.
  • If an anonymous user is disconnected, the user gets a new access pass when re-connecting.

The login access pass tracks the number of logins and runs over 28 days. For example, if 1000 logins are assigned to Group A, the users in Group A can use 1000 logins over 28 days. If 100 logins are consumed on Day 1, the 100 logins are available again on Day 29.

The maximum number of parallel user connections for a single user of this type of access pass is five (5). Note that this only applies to identified users. An anonymous user can only have one (1) user connection. When a user with the maximum number of parallel user connections ends a connection (for example, by logging out) five minutes must pass before the user can use the access pass to add another connection (for example, by logging in). However, a user can have more connections than allowed by a single access pass by consuming additional access passes.

One (1) token corresponds to ten (10) access passes. The access passes are allocated using login access groups in the QMC.

참고: App reloads will extend the session and consume access passes also when the app is not actively used. If a browser page is open with an app, app reloads will result in additional access pass consumption.