Sharing app content with anonymous access

With anonymous access, you can allow people outside of the Qlik Cloud tenant to access Qlik Sense app content. You can share apps as links that can be opened by anyone, or you can use qlik-embed to embed app content directly into other web pages and applications.

Anonymous access is controlled at the app level. Users with the correct permissions can turn anonymous access on and off as needed. These users can also configure access code settings, as well as view and copy links and codes that provide anonymous access.

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.

Use cases

Anonymous access allows public consumption of analytics without authentication. You can use anonymous access to share app content in the following ways:

• Create links to apps that can be opened to explore their sheets. Anyone with an internet connection can open these links.

• Generate embed codes that can be used to integrate app content directly into web sites and applications. The end result can be consumed without authentication to Qlik Cloud.

Anonymous access allows you to securely build and share Qlik analytics on a global scale. There are many possible use cases, including:

• An organization wants to provide a link within their website to a Qlik Sense app where anyone can access statistics about market trends or the organization's community impact.

• An organization wants to embed insights for a limited set of data into their public-facing website. For example, they could embed a visualization where users can view and interact with real-time data that is in the public domain.

Workflow

1. Build your app

   Create a Qlik Sense app with a data model and visualizations reflecting the data you want to show to external audiences.

   Creating analytics with Qlik Sense

2. Publish the app to a managed space

   When the base sheets and data structure are finalized, publish the app to a managed space. At this time, you can also configure how the app will be reloaded to reflect new data.

   Publishing apps

   Reloading app data

3. Activate anonymous access

   For each app that you want to make available with anonymous access, you need to first turn on anonymous access. When you do this, the app link and embed code become visible, and can be used.

   Turning anonymous access on and off

4. Option 1: Distribute the app link for anonymous access

   Sharing app links for anonymous access

5. Option 2: Use the embed code to integrate the app content into web sites and applications

   Sharing embed codes for anonymous access

Security considerations

When you make app content available with anonymous access, it becomes accessible without authentication to Qlik Cloud. In some cases (for example, in the case of embedding in websites), it becomes available to the public.

Consider the following best practices for data security when working with anonymous access:

• Do not share apps containing sensitive information via anonymous access.

• Use extra caution when loading data from shared data sources into apps, and then making it available with anonymous access. These data sources can change over time and you might not be aware of changes by other users.

Setting permissions

Tenant administrators control the ability of each user in the tenant to configure anonymous access for apps. They do this in the Administration activity center.

To allow a user in the tenant to generate app links that can be accessed by people outside the tenant, the Public link creation permission must be configured to Allowed for the tenant user. This procedure is performed by a tenant administrator.

This permission can be assigned in either of the following ways:

• Assigning the permission in the User Default role (affects all tenant users)

• Assigning the permission as a custom role (only affects tenant users with the custom role)

User Default role

Do the following:

1. In the Administration activity center, go to Users.

2. Switch to the Permissions tab.

3. Click User Default.

4. Expand Features and actions.

5. For Public link creation, use the drop down menu to modify the value.

6. Click Confirm.

Custom roles

Tenant administrators can also create custom roles to elevate the permissions for certain users above the User Default. As an administrator, you might want to restrict anonymous access permissions in the User Default, and then create a custom role to provide anonymous access permissions to a specific set of users.

Do the following:

1. In the Administration activity center, go to Users.

2. Switch to the Permissions tab and click Create new to create a new custom role.

3. Enter a Name, and optionally, a Description for the new role.

4. Under Permissions, expand Features and actions.

5. For Public link creation, use the drop down menu to select Allowed.

6. Click Confirm.

7. Switch back to the All users tab.

8. Select the checkboxes for the users whose permissions you want to modify.

9. Click Edit roles.

10. Assign the new custom role to specific users, and click Save.

Requirements

To work with anonymous access, you need:

• Access to a tenant created within a Qlik Anonymous Access subscription. Apps you want to share need to be located in this tenant.

• The required permissions in both the tenant and in the space where the app is located. See Permissions for configuring anonymous access.

• The app you are sharing for anonymous access needs to be in a managed space.

• If you are using qlik-embed, a specific OAuth client must be set up in the tenant. This needs to be done by a tenant administrator. See Creating an OAuth client for anonymous embeds of app content.

Permissions for configuring anonymous access

In Qlik Cloud Analytics, working with anonymous access involves the following:

• Turning anonymous access on and off for an app

• Managing access code settings

• Viewing and copying app and embed links

Permissions for toggling anonymous access

To turn anonymous access on and off for an app, you need the following space roles and administrator-assigned permissions:

• A value of Allowed for the Public link creation permission. This is assigned by a tenant administrator. You can receive the permission through the User Default settings or a custom role.

  For more information, see Setting permissions.

• One of the following space roles in the managed space where the app is located:

  • Owner (of space)

  • Can manage

Permissions for copying links

After anonymous access is turned on for an app, a user with one of the following space roles in the app's space can copy the link:

• Owner (of space)

• Can manage

• Can contribute

• Can view

• Has restricted view

• Can operate

For more information, see Copying an anonymous access link to an app.

Permissions for copying embed codes

After anonymous access is turned on for an app, a user with one of the following space roles in the app's space can copy the embed code:

• A value of Allowed for the Public link creation permission. This is assigned by a tenant administrator. You can receive the permission through the User Default settings or a custom role.

  For more information, see Setting permissions for users who can configure anonymous access.

• One of the following space roles in the managed space where the app is located:

  • Owner (of space)

  • Can manage

For more information, see Copying an embed code for an app.

Development of apps used for anonymous access

There are many options available for development of the apps you want to shared from a Qlik Anonymous Access tenant. For example:

• You can develop your app in the Qlik Anonymous Access tenant itself.

• The Qlik Platform Operations connector is also available for Qlik Anonymous Access tenants. With this Qlik Application Automation connector, you can develop your app in a different tenant, and then distribute it to the tenant from which you are sharing it anonymously. For more information about the connector, see Qlik Platform Operations connector overview.

Turning anonymous access on and off

When you turn anonymous access on, the app link and embed code become usable, and are made available for copying and distribution.

Do the following:

1. In Qlik Cloud Analytics, open the Insights or Analytics activity center.

2. Right-click the app, or click the icon next to it.

3. Click Share. The sharing dialog opens.

4. In the section Anyone with the link, use the toggle switch to activate and deactivate anonymous access.

Revoking anonymous access to an app

If you need to revoke access to the app by anonymous users, there are two actions you should consider: Deactivating anonymous access entirely, and resetting the access code.

Deactivating the app from anonymous access

When you turn off access entirely, the app will no longer be accessible by any user outside of the tenant. For instructions about turning off anonymous access, see Turning anonymous access on and off.

Resetting the access code

When you turn on anonymous access, the app link and embed code contain an access code. This access code does not expire. You can reset the access code so users with the old access code can no longer access the app, but users with the new access code can access it.

Resetting the access code affects both the app link and embed code.

Do the following:

1. In Qlik Cloud Analytics, open the Insights or Analytics activity center.

2. Right-click the app, or click the icon next to it.

3. Click Share. The sharing dialog opens.

4. In the section Anonymous access, click  to open the settings.

5. Click Reset access code.

After you have reset the access code, you can copy the new app link and embed code. Alternatively, return to the previous page in the dialog to copy them.

Viewing the apps in the space that are activated for anonymous access

Members of the managed space with the Owner and Can manage can see the apps that have anonymous access turned on. This is shown in Space details > Members. Anonymous access is listed as a space member.

Turn off anonymous access for an app by clicking next to the app and clicking Turn off.

Consuming content shared through anonymous access

For anonymous users to consume content, temporary app sessions are created to allow them access to the app. Each anonymous session lasts 15 minutes. For an anonymous user to continue analyzing content, they can refresh their browser, starting a new 15 minute session.

For more information about how anonymous users can navigate and explore app content, see Analyzing data without being added to a Qlik Cloud tenant.

Viewing the tenant's anonymous access capacity

Tenant and analytics administrators can view the tenant's purchased capacity for anonymous access. This information is shown in the Administration activity center.

For more information, see Anonymous access capacities.

Limitations

In the context of a Qlik Anonymous Access subscription, anonymous access has the following limitations:

• In Qlik Anonymous Access tenants, app developers can access many of the other capabilities that are available in Qlik Cloud tenants. A number of capabilities are not available in Qlik Anonymous Access tenants. For a list of what is available and unavailable, see Qlik Cloud Analytics specifications and capacity.

• With qlik-embed, you embed visualizations into external sources for anonymous consumption. When embedding visualizations for anonymous access, there are limitations for certain visualizations depending on the qlik-embed UI types. The same visualization-specific limitations also apply for anonymous access. In addition, the NL insights native object cannot be used in any embedding of app content for anonymous access.

  For more information about the limitations, see Visualizations.

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