Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Can you identify mobile-only user sessions in the Qlik Sense Enterprise on Windows Session Monitoring app?
The Sessions Monitoring App, on its own, does not distinguish sessions made by users on mobile devices.
If there is a specific need to separate mobile users and be able to track them reliably:
How To Grant Users The Access To Data Model Viewer.
With default security rules and settings, users can not see the data model for published apps. However, we can achieve this by creating/updating security rules through the Qlik Sense Management Console.
This requires a rework of the ContentAdmin rule and will provide far more permissions to users than Option 1. See ContentAdmin for details on what a ContentAdmin is allowed to do.
Attempting to connect to Gmail SMTP server over port 587, Amazon SES over port 587 and Office Mail 365 over port 587 using SSL, results in a connection error. This article explains what needs to be done in order to make this connection work properly.
Environment:
Email servers may require encryption when sending email.
Use the following steps to configure an SSL connection to an SMTP email service when using Publisher:
For Gmail, use port 587(smtp.gmail.com);Also the Gmail account needs to:
For Amazon Simple Email Service(SES), use port 587.
For Microsoft 365 service, use smtp.office365.com for address and port 587. Also see the following article for an alternative: Office 365 SMTP setup for Qlikview
Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.
Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.
This article provides information on available apps for each platform.
The Data Capacity Reporting App is a Qlik Sense application built for Qlik Cloud, which helps you to monitor the capacity consumption for your license at both a consolidated and a detailed level. It is available for deployment via the administration activity center in a tenant with a capacity subscription.
The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.
You can automate daily distribution of the latest app using the Capacity consumption app deployer template in Qlik Automate.
The Access Evaluator is a Qlik Sense application built for Qlik Cloud, which helps you to analyze user roles, access, and permissions across a tenant.
The app provides:
For more information, see Qlik Cloud Access Evaluator.
The Answers Analyzer provides a comprehensive Qlik Sense dashboard to analyze Qlik Answers metadata across a Qlik Cloud tenant.
It provides the ability to:
For more information, see Qlik Cloud Answers Analyzer.
The App Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Sense applications in your tenant.
The app provides:
For more information, see Qlik Cloud App Analyzer.
The Automation Analyzer is a Qlik Sense application built for Qlik Cloud, which helps you to analyze and monitor Qlik Application Automation runs in your tenant.
Some of the benefits of this application are as follows:
For more information, see Qlik Cloud Automation Analyzer.
The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.
The app provides:
For more information, see The Entitlement Analyzer.
The Reload Analyzer is a Qlik Sense application built for Qlik Cloud, which provides an overview of data refreshes for your Qlik Cloud tenant.
The app provides:
For more information, see Qlik Cloud Reload Analyzer.
The Report Analyzer provides a comprehensive dashboard to analyze metered report metadata across a Qlik Cloud tenant.
The app provides:
For more information, see Qlik Cloud Report Analyzer.
Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:
For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.
The OEM Dashboard is a Qlik Sense application for Qlik Cloud designed for OEM partners to centrally monitor usage data across their customers’ tenants. It provides a single pane to review numerous dimensions and measures, compare trends, and quickly spot issues across many different areas.
Although this dashboard is designed for OEMs, it can also be used by partners and customers who manage more than one tenant in Qlik Cloud.
For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.
With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.
If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.
The Operations Monitor loads service logs to populate charts covering the performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.
The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.
The Content Monitor loads from the APIs and logs to present key metrics on the content, configuration, and usage of the platform, allowing administrators to understand the evolution and origin of specific behaviors of the platform.
All three apps come pre-installed with Qlik Sense.
If a direct download is required: Sense License Monitor | Sense Operations Monitor | Content Monitor (download page). Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows.
The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.
Basic information can be found here:
App Metadata Analyzer (help.qlik.com)
For more details and best practices, see:
App Metadata Analyzer (Admin Playbook)
The app comes pre-installed with Qlik Sense.
Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.
LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs
Sessions Monitor, Reloads-Monitor, Log-Monitor
Connectors Log Analyzer
All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.
A space owner can edit apps owned by other users, but cannot edit the scripts. The option to access the Data Load Editor is not present:
Explicitly assign the Can edit data in applications space role. See Working in shared spaces | help.qlik.com for details.
The Owner role implicitly gives access to all other actions on the space except this one. This is designed to prevent owners from accidentally accessing another user's script without them or another space manager taking explicit responsibility.
The existing 'has restricted view' space role can export data to Excel. If you do not wish for users with the 'has restricted view' space role to be able to export data, you will need to edit the User Default role to deny download for all users, and then create a custom role that allows it for specific users and groups.
Steps
This has now changed the default user behavior across the tenant. Users will no longer be able to download in-app content.
This creates a new role that you will need to assign to any users who should have the permission to download in-app content.
There is no function to restrict downloading by apps or spaces.
A Professional or Full entitlement was removed without any action from the tenant administrators.
Going to the Administration activity center and reviewing Events by filtering for the Event Type "com.qlik.license.assignment.deleted" or "com.qlik.license.assignment.updated" shows no activity.
Always align entitlements between your environments.
If the same Signed License Key is also used by another tenant or on a version of Qlik Sense Enterprise for Windows, any change from those other environments will be synchronized to your tenant.
Because the action was not performed on the tenant itself, the tenant's Events section (or the Audit APIs) won't show them.
The HubSection_Home resource filter in Qlik Sense refers to the button which allows a user to navigate back to the Hub from inside of an application.
Default ruleset:
If an administrator should want to disable this functionality for their users, for example, if the application is embedded into another page. Then they will want to disable the default rule named HubSections.
The result with this rule disabled is as follows for the end user:
The result of this change will disable this functionality for all users. If an administrator wants to provide this functionality to a select set of users then the administrator can create a new rule in this schema:
For the Execute Automation button, a maximum of 100 automations can be displayed for selection under Automation.
If you have access to more than 100 automations and cannot find the automation you want, you can use the automation ID. The automation ID is in the segment after /editor/ in the URL before /edit or /history.
For example, in qlik.com/automations/editor/6c201b49-cz2e-00dc-8040-464ca41457b0/edit?resourceName=Active%20Intelligence, the automation ID is 6c201b49-cz2e-00dc-8040-464ca41457b0.
For more information about identifying automation IDs, see How to identify the automation Id and job Id in Qlik Application Automation.
Qlik Help entry: Creating Buttons
QVS files (read more) cannot be uploaded to Managed Spaces in Qlik Cloud.
.qvs (QlikView Script) files cannot be directly uploaded to a managed space in Qlik Cloud. QlikView Script files are intended as reusable load script blocks and are not considered application files (such as .qvf and .qvw).
To use a .qvs file, copy the script's contents into an app's load script editor or use an $(Include=...) statement to reference the file, which needs to be stored elsewhere and made accessible to the app.
This article aims to answer the following questions:
Stitch is a cloud-based ETL platform, which means it is not real-time and may experience latency due to the nature of cloud infrastructure and its step-based processing model.
Stitch’s replication process consists of three independent steps:
Extraction → Preparation → Loading
Each step takes time to complete and is influenced by various factors.
For more information, see: Stitch’s Replication Process | stitchdata.com
The speed and efficiency of Stitch’s replication process can be affected by:
These factors can vary over time and across integrations, which is why replication durations are not always predictable.
The replication frequency determines how often Stitch initiates a new extraction job (when one isn’t already in progress). Stitch tracks your tables and updates them based on the replication method you’ve selected.
However, this frequency does not guarantee that data will be prepared and loaded within the same time window. For example, a 30-minute frequency does not mean the full replication cycle completes in 30 minutes.
Stitch extracts one table at a time per integration (sequentially). It must finish extracting one table before moving to the next.
Once data is extracted, Stitch begins the preparation phase, which involves cutting records into rectangular staging files. This step is batch-based and starts as soon as data is returned from the source. The duration of this phase depends on the structure and volume of the data.
Stitch can load up to 5 tables concurrently per destination. If 5 tables are already loading, others must wait until a slot becomes available. For example, with 10 integrations and 20 tables each, Stitch will load 5 tables at a time per destination.
Stitch’s loading systems check every 15–20 minutes for batches of records that are fully prepared and ready to be loaded into your destination.
What may appear as missing data is often just incomplete processing. Most data discrepancies resolve themselves once Stitch finishes processing.
This template was released on September 29, 2025.
Many customers rely on the Capacity Consumption Report in Qlik Cloud to understand usage and billing patterns. Until now, deploying and refreshing this app required repetitive manual steps: downloading from the admin console, publishing it into a managed space, and re-publishing every time a new version was needed.
This approach made monitoring difficult and often left customers with out-of-date insights.
A new Qlik Automate template automates the end-to-end deployment of the consumption app into a managed space of your choice. Once set up, the app is refreshed daily - ready for admins or billing users to work with.
With this in place, you can:
Stay current – The app refreshes once per day (morning CET), so your analytics reflect the latest usage data.
Collaborate easily – Place the app directly into a managed space for shared access.
Enable subscriptions and alerts – Users can subscribe to sheets or KPIs, or create alerts on thresholds that matter to them.
Maintain governance – The template creates/uses the right spaces and applies roles automatically.
Eliminate manual work – No more re-publishing or searching through personal space copies.
The automation checks that you are on a capacity-based subscription (your app size must be 100MB or less; larger data sets still need to be deployed manually or via script).
It ensures you are a TenantAdmin (required for license and app access).
It creates a staging space (for imports) and a managed space (for sharing).
It imports the latest version of the app into staging, then publishes it to the managed space.
You can configure how many historic versions you want to keep in the shared space. By default, no staged apps are kept.
Since the underlying data is refreshed once per day in the morning CET, we recommend scheduling this automation to run around midday CET. This ensures that your managed space always holds the latest daily version of the app.
TenantAdmin role
Capacity-based subscription
Report size ≤100MB (larger reports cannot currently be deployed with Qlik Automate)
Create a new automation, navigate to the App Installer category, and select the Capacity consumption app deployer template.
Update the variables (space names, versions to keep).
Test manually once.
Schedule it to run daily (around midday CET).
Once enabled, you’ll have a single source of truth for consumption reporting - ready to drive alerts, subscriptions, and collaborative analysis across your admins.
This article is provided as is. For further customization or assistance, reach out to Qlik's Professional Services or engage in our Qlik Sense Administration and Configuration forum.
This details the steps required to use a Microsoft Excel (XLS) file as a User Directory in the User Directory Connector (UDC).
The instructions in this article are written for Microsoft Office 2016, which has reached end of life as of October 2025. As an alternative, use Microsoft 365 Access Runtime. See Download and install Microsoft 365 Access Runtime.
The required Microsoft Excel Driver may not be installed by default.
Do not change them, or the import will fail.
The following errors you may be logged in C:\ProgramData\Qlik\Sense\Log\Repository\Trace\<SERVER>_UserManagement_Repository.txt
Verify that the name and userid columns in the file are correctly named and have not been renamed.
Is it possible to migrate users and data connections from one Qlik Cloud Analytics tenant to another?
You cannot migrate users and data connections from an existing tenant to a newly purchased tenant.
The following will need to be done:
What about apps and scripts?
Apps can be migrated from one tenant to another using the following Qlik CLI automation: Migrate apps between Qlik Cloud tenants
This tutorial is not exhaustive, and does not migrate other resources such as spaces, automations, data alerts, subscriptions, notes, etc. Qlik offers solutions via Qlik Professional Services for complete tenant to tenant migrations.
For scripts, follow the process of exporting them manually from the old tenant and then importing them to the new tenant. See Exporting scripts.
To make the process easier for you, Qlik's customer support team can link the newly purchased tenant license to a trial tenant, and you can continue to use the trial tenant. The trial tenant will be updated to a Standard, Premium, or Enterprise version after linking the license (depending on which package was purchased).
Do you need iterative planning and support assistance?
If you're looking to perform a manual transfer but need assistance with iterative planning or direct engagement by Qlik, our Professional Services are ready to assist.
The "Enable IP Allowlist" option has been enabled, and several IPs have already been added to the list to restrict access solely to those on the allowlist. However, other IPs are still able to access TMC.
To configure an IP allowlist in Talend Management Console, the user account needs to possess the Security Administrator role.
Only accounts granted the "Users - Manage" permission can bypass the IP allowlist. (This permission is encompassed within the Security Administrator role.).
Once the IP allowlist is enabled, the same user account must take one of the following actions:
Either create additional users without the "Users-Manage" permission, Or remove its own Security Administrator role.
This guarantees that the IP allowlist is effectively enforced for the account.
Consequently, IP addresses not included in the IP allowlist will be unable to connect to TMC, as illustrated below:
Setting up IP allowlist policy to restrict user access
***Changes must be made to all Qlik servers that will not be provided with internet access.***
For servers not connected to the internet, they may be prompted with a pop-up error when browsing in the Hub or in the Data Load Editor with the following errors:
Browser Debug tools may display the following error in the console:
This was originally defined as an issue with the Qlik Sense DataMarket connector executable, which is cryptography signed for authenticity verification, and the .NET Framework's verification procedure when launching an executable includes checking OCSP and Certificate Revocation List information, which means fetching it online if the system doesn't have a fresh cached copy locally.
Even without the QlikData Market being in use, the solutions provided can be deployed when encountering issues with Qlik Sense Enterprise Windows servers that have no internet access. Internet access is recommended.
Only deploy one of the below options.
Option 1 will persist through upgrades, whereas Option 2 would have to be reapplied after every Sense upgrade.
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime>
<runtime> <generatePublisherEvidence enabled="false"/> </runtime>
<runtime> <some other key="value"/> <generatePublisherEvidence enabled="false"/> </runtime>Example:
<runtime>
<generatePublisherEvidence enabled="false"/>
</runtime><runtime>
<generatePublisherEvidence enabled="false"/>
</runtime><runtime>
<some other key="value"/>
<generatePublisherEvidence enabled="false"/>
</runtime>For Qlik Versions 2.x.x [mid-2016 and older]... this will fully disable Qlik Sense DataMarket:
Qlik Sense Enterprise on Windows facilitates the export of an Audit from the Qlik Sense Management Console. See Exporting audit query results.
This export works as expected unless the Audit result is filtered by one app and one user. If only one user and one app are used in the filter, the resulting Excel file is empty.
This is a known defect (QCB-32416), which is expected to be fixed in a future release. Review the Qlik Sense Enterprise on Windows Release Notes for details.
Filter by more than one app and one user.
Product Defect ID: QCB-32416