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

Setting up Qlik Sense Mobile SaaS

When you start the Qlik Sense Mobile SaaS app for the first time, you must connect and authenticate to a Qlik Cloud tenant before you can consume Qlik Sense apps on your mobile device.

After you have connected once, you can open the mobile app when you are offline, and view Qlik Sense apps that you have downloaded.

Technical and security considerations

OS support

Qlik Sense Mobile SaaS supports the following operating systems:

  • iOS/iPadOS 16 or later

  • Android 12 or later

Number of concurrent devices

Each user can be logged on to Qlik Sense Mobile SaaS on five concurrent mobile devices per tenant.

If you delete the Qlik Sense Mobile SaaS app from your device without having logged out first, a second device license will be consumed when you reinstall the app.

Qlik Sense Mobile SaaS login longevity

The OAuth protocol and refresh-token architecture used by Qlik Sense Mobile SaaS to communicate with Qlik Cloud means that most Qlik Sense Mobile SaaS users do not have to log in each time they open their mobile app.

Users are automatically logged out if:

  • The user is inactive for 7 days without using the app.

  • The identity provider application configuration is incomplete.

  • The administrator explicitly revokes the user's access.

On-demand apps

On-demand apps may not work as expected in Qlik Sense Mobile SaaS.

Direct Query apps

Direct Query apps are not supported in Qlik Sense Mobile SaaS.

Security

The Qlik Sense Mobile SaaS app is protected by a Qlik Sense password when you connect to a Qlik Sense tenant. For additional security, especially when working offline, you can turn on app lock to use PIN or biometric authentication to unlock the Qlik Sense Mobile SaaS app. See Unlocking the app with a PIN or biometric.

Tip noteProtect your data by ensuring that your device is protected with a password or biometric. Lock the device when not in use or log out from Qlik Sense Mobile SaaS.
Information noteThe tablet or phone must have a password or screen locking enabled to install and run Qlik Sense Mobile SaaS.

Object rendering

Visualizations in Qlik Sense Mobile SaaS can be rendered natively or in an embedded WebView.

Natively rendered visualizations have better performance compared to visualizations rendered in WebView. Natively rendered visualizations are:

  • Button

  • Filter pane

  • KPI

  • Table

  • Text & image

  • Treemap

If a natively rendered visualization is wrapped inside a Container object, it will be rendered in an embedded WebView.

Natively rendered visualizations do not support CSS styles in custom themes.

Connecting to a Qlik Sense subscription

After you have downloaded the Qlik Sense Mobile SaaS app, you create a connection to your Qlik Sense subscription. You can have more than one connection.

  1. On the start page, tap +.

    If this is the first connection, tap Login.

  2. Define the Qlik Sense URL, in the following form: tenant.qlikcloud.com. Add a friendly name for the tenant. Tap Add.

Logging in to Qlik Sense

After you have added the connection to your Qlik Sense subscription, you must log in using your Qlik Sense credentials.

  1. On the start page, tap the Qlik Sense subscription. The login page is displayed.

  2. Enter your username and password and tap Login.

Information noteOffline login is possible until 7 days after the last login.

Unlocking the app with a PIN or biometric

For added security, you can turn on app lock to use your device authentication method (PIN, fingerprint, or face) with the Qlik Sense Mobile SaaS app. Protecting the app with a PIN or biometric helps to prevent unauthorized users from accessing the app. When turned on, you must unlock the app using either a PIN or biometric when opening or switching to the app. Unlocking the app is required whether you are connected to the tenant or working offline. You must set up fingerprint or face authentication for your device to use app lock with Qlik Sense Mobile SaaS.

  1. Tap your profile icon in the mobile app to open the Settings page.
  2. You can also tap Settings on the start page.

  3. Under App lock, turn on Unlock with PIN, fingerprint, or face authentication.
Information noteIf fingerprint or face authentication does not unlock the app, you can enter your PIN.

Using Qlik Sense Mobile SaaS while offline

If enabled in your Qlik Sense tenant, you can still open Qlik Sense Mobile SaaS and view the Qlik Sense apps you have downloaded while being disconnected or offline.

Offline functionality is enabled by the tenant admin in the Administration activity center, see Enabling offline access to apps.

You must log in to the tenant at least once before you can open Qlik Sense Mobile SaaS offline. Offline login is then allowed for 7 days since the last online login.

  1. Download an app to your mobile device.

  2. Turn on Airplane mode on your device, or disconnect from the server.

  3. Test the app to ensure that the app works as expected.

Logging out

  1. Tap your profile icon in the mobile app. The Settings page opens.
  2. Tap Log out. You are logged out, and the start page opens.

Editing a subscription connection

  1. On the start page, long-touch and swipe left on the connection you want to edit.
  2. Tap update. The Update server page opens.
  3. Update the URL and the friendly name as required. Tap Update.

Removing a subscription connection from the list

When you delete an existing connection from your Qlik Sense Mobile SaaS app, any locally downloaded apps from this tenant will be deleted as well.

  1. On the start page, long-touch and swipe left on the tenant connection you want to remove.
  2. Tap delete.
  3. Tap Confirm. The Qlik Sense tenant connection is deleted from your Qlik Sense Mobile SaaS app.

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!