Early Access: The content on this website is provided for informational purposes only in connection with pre-General Availability Qlik Products.
All content is subject to change and is provided without warranty.
Skip to main content Skip to complementary content

Qlik Anonymous Access specifications and capacity

This topic outlines the specifications and capacities for Qlik Anonymous Access subscriptions.

There are some differences between Qlik Anonymous Access subscriptions and other Qlik Cloud subscriptions. While you might need to consider some of the same requirements as for a capacity-based subscription, Qlik Anonymous Access subscriptions also require attention to capacities for anonymous access, including:

  • Maximum memory that can be consumed concurrently by all apps

  • Maximum number of app sessions being consumed concurrently by all anonymous users

For more information about these metrics, see Understanding the subscription value meters. For information about differences between Qlik Anonymous Access and capacity-based subscriptions, see Differences between Qlik Anonymous Access and capacity-based subscriptions.

Terminology on this page

The following terminology is used in content about anonymous access:

  • Anonymous users: Users who are accessing app content anonymously, either through anonymous access links to an app or by consuming embedded analytics anonymously. These users are not members of the Qlik Cloud tenant, and also do not require Qlik accounts.

  • Tenant users: Users who are members of the tenant, who manage the tenant and develop analytics for consumption by anonymous users. Tenant users are users with Full User entitlement or specific administrator privileges in the tenant.

Available capabilities

This section describes the capabilities that are available for tenant users and anonymous users in Qlik Anonymous Access.

Tenant users

Available capabilities for tenant users

The following features are available to tenant users:

  • A personal space to create your own content

  • Group collaboration in shared spaces where team members can develop and share apps

  • Full Qlik Sense analytic capabilities, including Insight Advisor, Alerting, and Notes

  • Drag-and-drop app creation and fully interactive apps

  • Many of Qlik’s augmented intelligence capabilities, including Insight Advisor Chat and insight suggestions

  • Access to Qlik Talend Data Integration for creating QVD files in a Qlik Cloud data platform. The QVD files can be used in analytics apps.

  • Direct data connectivity to over 40 data sources

  • Data movement to Qlik Cloud from relational database sources and SaaS sources.

  • Qlik Application Automation: The basic tier of Qlik Application Automation is included with a Qlik Anonymous Access subscription.

  • Script interface

  • Catalog tools (Dataset viewer, impact analysis, lineage)

  • Business glossaries

  • Automated data refreshes

Available with additional purchase

The following are not included in a Qlik Anonymous Access subscription, but can be added with an additional purchase:

  • Qlik Reporting Service

  • Qlik Geocoding

For more information, contact your Qlik account representative.

Unavailable capabilities for tenant users

The following features are not available for any tenant user:

  • In-app capabilities:

    • Key driver analysis

  • Qlik Answers

  • Qlik AutoML, including Qlik AutoML analytics connector

Anonymous users

Available capabilities for anonymous users

Anonymous users have access to limited versions of the Qlik Sense apps shared with them. In these apps, they have restricted permissions, and certain capabilities are not available. Other than apps, they do not have access to any other capability in Qlik Cloud.

The permissions granted to an anonymous user allow them to open and consume apps, sheets, or visualizations (depending on use case), making selections and applying public bookmarks. For more information about what anonymous users can do in an app, see Managed space permissions for anonymous users.

Unavailable capabilities for anonymous users

The following in-app capabilities are available in anonymous access tenants. However, they are not available for anonymous users when they open or consume app content.

  • Storytelling

  • Notes

  • Insight Advisor

  • Key driver analysis

  • NL insights visualization

  • Reporting

  • Alerts

  • Subscriptions

  • Associative insights

Besides apps in this restricted format, all other Qlik Cloud capabilities are unavailable for anonymous users.

Qlik Cloud guardrails

Guardrails are hard limits on capacities. They are used to ensure Qlik Cloud performance and stability, for example, by limiting parallel reloads to avoid extensive load.

The guardrails for Qlik Anonymous Access are shown in the tables below. They are separated into:

  • Primary guardrails: Capacities that are directly related to, or affected by, anonymous access capabilities.

  • Additional guardrails: Capacities that apply to Qlik Anonymous Access subscriptions, but are not unique to them. Some of these guardrails also apply to other Qlik Cloud subscriptions.

Primary guardrails

Primary guardrails for Qlik Anonymous Access
Capacity Qlik Anonymous Access

App size (in-memory) limit

Information note

Large app support is not available in Qlik Anonymous Access subscriptions.

1 GB
User session time-out (anonymous sessions) 15 min
User session time-out (tenant user sessions) 30 min
Maximum number of apps that be opened concurrently 50
Number of tenants 1

Engine hypercube memory limit

Information noteThe standard hypercube memory limit in Qlik Cloud is 10 GB. However, for Qlik Anonymous Access, this limit is affected by the app size (in-memory) limit of 1 GB.
1 GB

App file size limit for upload from other versions of Qlik Sense via the Analytics activity center

Information note

This limit pertains to the disk size occupied by app files, rather than the in-memory limit.

200 MB

Additional guardrails

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!