--- Brand: klarmetrics.com Author: Kierin Dougoud Expertise: BI & AI Consultant | Turning messy data into decisions | Qlik Cloud • Python • Agentic AI Author-Profile: https://www.linkedin.com/in/mkierin/ Canonical-URL: https://klarmetrics.com/qlik-sense-reporting-guide/ --- # Qlik Sense Reporting: The Complete Guide to Every Option in 2026 # Qlik Sense Reporting: The Complete Guide to Every Option in 2026 Qlik reporting in 2026 covers a lot more ground than most users realise. There are subscriptions for self-service delivery, in-app enterprise reporting with burst capability, Automate-powered workflows for external distribution, native data alerts, and a newly native PixelPerfect designer. Each option solves a different problem. Pick the wrong one and you’ll hit a wall fast, usually right before a stakeholder deadline. This guide maps every built-in reporting option in Qlik Cloud, explains exactly what each one does and does not do, and helps you choose the right approach for your use case. # Quick Decision Guide: Which Reporting Option Should You Use? Use this table to find the right option before diving into the details below. Use case Recommended option Key requirement Users want to subscribe themselves to a sheet or chart Subscriptions Recipients must be Qlik Cloud users Send reports to people without a Qlik account Qlik Automate Premium or Enterprise tier Pixel-perfect PDF (compliance, branded, executive) In-app reporting: PixelPerfect Qlik Cloud Analytics subscription Formatted Excel output with custom layout In-app reporting: Tabular Qlik add-in for Excel Burst reports (same report, different data per person) In-app reporting (burst) or Automate Up to 500 unique reports per task Alert when a KPI crosses a threshold Native data alerts Teams/Slack requires Automate routing Post reports to Teams or Slack automatically Qlik Automate Premium or Enterprise tier Replacing NPrinting See [NPrinting migration guide](https://klarmetrics.com/qlik-nprinting-end-of-life/) EOS: February 2027 # Qlik Cloud Subscriptions: Self-Service Scheduled Reports **Subscriptions** are the lightest-weight reporting option in Qlik Cloud. Any user with a Professional or Analyzer entitlement can subscribe themselves to a chart or up to 10 sheets from any app they can access, and receive a PDF or PowerPoint snapshot on a defined schedule. No developer involvement is needed once an admin has enabled the feature. Users set their own schedule (daily, weekly, or monthly), pick their selections, and the report lands in their inbox at generation time. # What subscriptions can and cannot do Subscriptions are straightforward but come with hard limits that catch people out regularly. * Output formats: PDF (300 DPI) and PowerPoint (.pptx) only * Selections saved in a subscription recalculate against current data at generation time, so expression-based filters stay dynamic * Maximum of 100 subscriptions per user, 10 sheets per subscription, 100 recipients per subscription * Maximum execution time per subscription: 2 hours The most important limitation: **recipients must be Qlik Cloud users** with a valid email address configured in the tenant. There is no way to send a subscription to an external email address. If you need to deliver to people without Qlik accounts, that is an Automate job. Certain object types are also excluded from subscription output: filter panes, tab containers, navigation menus, and dynamic (associative container) charts will not appear in the generated file. # In-App Reporting: Enterprise-Grade Distribution **In-app reporting** is the centrally managed, admin-controlled reporting system inside Qlik Cloud. It lives under the “Prepare” tab in any Qlik Sense app and supports five template types, burst reporting up to 500 unique reports per task, and distribution to both email and SharePoint. This is the right choice when a developer or admin owns the reporting process, rather than individual users. It scales significantly beyond subscriptions. # Template types and output formats In-app reporting supports multiple template types, each with different output options and authoring tools. Template type Authored in Output formats Best for Tabular (Excel) Qlik add-in for Microsoft Excel .xlsx, PDF Data tables, financial reports, row-level output PixelPerfect Embedded PixelPerfect designer PDF only Compliance-grade, branded, formatted PDFs PowerPoint Microsoft PowerPoint .pptx, PDF Presentation-ready slide decks Word Microsoft Word .docx, PDF Narrative reports with embedded charts HTML Embedded HTML editor Email body HTML, file-based HTML Rich email-body reports Template size limits apply: Excel, PixelPerfect, and HTML templates are capped at 10 MB. PowerPoint and Word templates allow up to 30 MB. # Burst reporting: one task, many personalised outputs **Burst reporting** lets a single report task send personalised versions to multiple recipients. Each person in the distribution list is assigned a named “report filter,” similar to a saved bookmark but purpose-built for reporting. One task can produce up to 500 unique reports from the same template, with different data slices per person. This is particularly useful for regional or account-level distribution where the report structure is identical but the data must be filtered per recipient. For internal Qlik Cloud users, [Section Access](https://klarmetrics.com/25-qlik-section-access/) still applies as an additional security layer on top of report filters, so a recipient cannot receive data they are not authorised to see. # Distribution channels In-app reporting can deliver to email (requires an SMTP provider configured at tenant level) and Microsoft SharePoint (via an Office 365 connection, no file size limit). Users can also trigger on-demand report generation directly from within an app, without waiting for a scheduled task. # What in-app reporting does not support There are object types that the Qlik Reporting Service cannot render, and this is a common source of frustration for teams migrating from NPrinting. * Filter panes and maps are not supported * Charts using Tree, Pivot, or Stacked hypercube types are excluded * **Third-party extensions (Vizlib, etc.) cannot be exported** via the Qlik Reporting Service. This is an official limitation confirmed in the Qlik support documentation * Apps using Direct Query are not supported * Macros/scripts in Excel templates are stripped on upload If your dashboards rely heavily on third-party extensions, in-app reporting is the wrong tool. See the third-party options section at the end of this guide. # How Does Qlik Application Automation Handle Reporting? **Qlik Application Automation** (Qlik Automate) handles reporting through a dedicated Qlik Reporting connector inside any automation workflow. Two blocks were added in late 2024/early 2025: “Get PixelPerfect Report” and “Get Tabular Report.” The generated file is passed directly to a distribution block in the same workflow. Automate is the right tool when you need to go beyond the limits of subscriptions or in-app reporting, particularly for external recipients, cloud storage delivery, or Teams and Slack distribution. For a broader look at what works and what does not across the full reporting stack, see the guide to [finance reporting automation](https://klarmetrics.com/finance-reporting-automation/). # What Automate can do that the other options cannot * **Send to any email address**, not just Qlik Cloud users. External recipients require no Qlik account * Attach reports to **Microsoft Teams** channel messages (see the [Qlik Automate Slack integration](https://klarmetrics.com/qlik-automate-slack-integration-tutorial/) for similar Slack patterns) * Deliver to cloud storage: Amazon S3, Dropbox, Google Cloud Storage, FTP/SFTP * Loop across dimension values to generate one report per region, product, or any other dimension — automatically * Pull external recipient lists from Office 365, a database, or a spreadsheet * Trigger on events: after a data reload completes, after a webhook fires, or on a custom cron schedule For a step-by-step walkthrough of email delivery via Automate, the [Qlik Automate email automation](https://klarmetrics.com/qlik-automate-email-automation-tutorial/) tutorial covers the full setup including attachment handling and dynamic recipient logic. # Automate reporting availability Reporting blocks in Automate are not available in Qlik Cloud Analytics Starter or Standard editions. You need a **Premium or Enterprise tier** (or the relevant add-on) to access the Qlik Reporting connector. Report automations also save to personal spaces only, so shared-space automation for reporting requires a workaround at the architecture level. # Native Data Alerts: Condition-Based Notifications **Native data alerts** are condition-based monitors, not scheduled reports. They fire when data meets a defined threshold or condition, not on a fixed calendar. This distinction matters: alerts are for exception reporting, not regular distribution. Use case: “notify me if revenue drops more than 10% compared to last week.” That is an alert. “Send the weekly sales summary every Monday at 07:00” is a subscription or in-app report. # How alert conditions work Alert conditions can compare a measure against a fixed value, an expression, another measure, or the result of a previous evaluation (useful for week-on-week or period-on-period comparisons). Conditions can be combined with AND/OR logic and grouped into multi-step sequences. Alerts evaluate either on a fixed schedule (daily, weekly, monthly) or data-driven, meaning they fire when the app data changes after a reload or republication. # Notification channels for native alerts Native Qlik Cloud data alerts send to three channels: web browser push notification, mobile push notification (via the Qlik Cloud mobile app), and email (including a daily digest mode that batches multiple alerts into one message). **Teams and Slack are not directly supported by native alerts.** To route an alert to Teams or Slack, you need to connect the alert to a Qlik Automate workflow: alert fires, triggers automation, automation posts to the channel. It is a two-step setup but works reliably once configured. Note: there is also a separate standalone “Qlik Alerting” product (available via the AWS Marketplace) with a more advanced rules engine and broadcast notifications. That is a distinct product from the native Qlik Cloud data alerts described here. # PixelPerfect Reporting in Qlik Cloud: Now Native **PixelPerfect reporting is now native in Qlik Cloud** as of 2024-2025. This is the most significant change to the Qlik reporting stack in recent years. Previously, pixel-level control over report layout required NPrinting. That dependency is gone. The embedded PixelPerfect designer uses a banded layout system: horizontal and vertical bands structure the report, and content binds dynamically from the connected Qlik app. Output is PDF only. # What native PixelPerfect does well * Precision layout for compliance reports, executive summaries, and customer-facing documents * Dynamic data binding across band repetitions (repeat a section per dimension value, similar to NPrinting PixelPerfect behaviour) * Available both task-based (centrally scheduled) and on-demand (user-generated within the app) * Burst reporting is supported: the same template with different data filters per recipient * Templates can be migrated from NPrinting PixelPerfect using the QPXP export format (requires NPrinting February 2025 or later) # Known gaps vs. NPrinting PixelPerfect * Scripts in templates are removed on upload. If your NPrinting PixelPerfect templates use scripting, that logic needs to be rebuilt * Third-party extension visualisations are not rendered * Output is PDF only. NPrinting also supported HTML and Word output from PixelPerfect templates * Custom CSS is not included The template migration path works for structure and layout, but job configurations (filters, schedules, dynamic naming, cycling) are not imported from NPrinting. Those must be rebuilt in Qlik Cloud. If you are planning a migration, the [NPrinting migration guide](https://klarmetrics.com/qlik-nprinting-end-of-life/) covers which template types transfer cleanly and which need a rebuild. # What About Qlik Answers and Insight Advisor? [Qlik Answers](https://klarmetrics.com/qlik-answers-agentic-ai/) and Insight Advisor are not reporting tools. They address a different use case entirely: on-demand, conversational analytics, not scheduled distribution. Insight Advisor is built into Qlik Cloud apps and responds to natural language questions about the current dataset (“show me revenue by region this quarter”). It generates chart suggestions and natural language summaries of what a chart shows. Useful for ad-hoc exploration, not for regular report delivery. Qlik Answers (launched 2024) focuses on unstructured data: PDFs, Word documents, HTML pages. Users ask questions in natural language; Qlik Answers retrieves and synthesises answers from those documents with source citations. There are no scheduled outputs, no email delivery, and no distribution workflows. The two are being brought closer together on the roadmap (structured plus unstructured NL query in one interface), and the [Qlik MCP Server](https://klarmetrics.com/qlik-mcp-server-guide/) opens up programmatic access to that capability for developers building external integrations. Neither replaces a reporting workflow. Do not conflate them. # Third-Party Options for Reporting Gaps Three limitations in native Qlik Cloud reporting are severe enough that third-party tools are a legitimate solution for some teams. The biggest gap: **third-party extensions**. If your dashboards use Vizlib, Climber, or similar extension libraries, neither subscriptions nor in-app reporting can render those objects. The Qlik Reporting Service officially does not support extensions from the marketplace or custom-built visualisations beyond the native set. **Qalyptus** is the most commonly referenced solution for this gap. [Qalyptus Cloud](https://www.qalyptus.com/products/qalyptus-cloud) supports all Qlik objects including third-party extensions and outputs Excel, Word, PowerPoint, HTML, and PDF. It is available as a SaaS product on the Microsoft AppSource marketplace. Other tools worth knowing: **Mail & Deploy** (established NPrinting migration alternative with complex scheduling) and **ancoreShare** (distribution and automation). These are worth evaluating if Automate’s capabilities do not fit your workflow or if your organisation is not on a Premium/Enterprise tier. # Full Feature Comparison Feature Subscriptions In-App Reporting Qlik Automate Data Alerts Who sets it up User (self-service) Developer/Admin Developer User/Developer Output formats PDF, PowerPoint Excel, PDF, PPT, Word, HTML PDF, PPT, Excel (via blocks) Notification + link Burst reporting No Yes (up to 500) Yes (via loop) N/A External recipients No No Yes No Teams/Slack delivery No No Yes (native) Via Automate only SharePoint delivery No Yes Yes No PixelPerfect output No Yes (native designer) Yes (via block) N/A Third-party extensions No No No N/A Trigger type Schedule Schedule + on-demand Schedule + event + webhook Condition + schedule License tier required All tiers Standard+ (metered) Premium+ All tiers # Frequently Asked Questions # Can Qlik Cloud send reports to people without a Qlik account? Not with subscriptions or in-app reporting. Only Qlik Automate supports delivery to external email addresses with no Qlik account required. That requires a Premium or Enterprise tier. For external distribution on lower tiers, a third-party tool (Qalyptus, Mail & Deploy) is the alternative. # Does in-app reporting support Vizlib or other third-party extensions? No. Third-party extensions cannot be rendered by the Qlik Reporting Service. This applies to subscriptions and in-app reporting equally. It is an official limitation, not a configuration issue. Qalyptus is the most widely used solution for dashboards built on extension libraries. # What is the difference between a subscription and a data alert? A subscription sends a scheduled snapshot regardless of what the data shows. A data alert fires only when a condition is met, for example when a KPI drops below a threshold. Use subscriptions for regular reports, and use alerts for exception monitoring where you only want to be notified when something changes. # Is PixelPerfect reporting still only available in NPrinting? No. PixelPerfect is now native in Qlik Cloud as of 2024-2025. The embedded designer supports banded layout, dynamic data binding, burst reporting, and PDF output. Templates can be migrated from NPrinting (QPXP format, requires NPrinting February 2025+), though job configurations (schedules, filters, cycling) must be rebuilt manually. The [NPrinting migration guide](https://klarmetrics.com/qlik-nprinting-end-of-life/) covers the full migration process. # Does Qlik Automate reporting need a specific date dimension or calendar setup? Automate itself does not require a particular data model structure. However, if your report content depends on accurate time-based filtering, for example showing “this week vs. last week” or fiscal period data, having a well-built [master calendar](https://klarmetrics.com/15-qlik-master-calendar/) in the underlying app will make those selections behave predictably when Automate applies them at generation time. # The Right Tool Depends on Who Controls the Process The clearest way to think about Qlik Cloud reporting is by who owns the setup. **Subscriptions** are for users who want control over their own scheduled snapshots. **In-app reporting** is for developers and admins who manage centralised distribution with structured templates. **Automate** is for teams that need to reach outside the Qlik ecosystem: external recipients, cloud storage, Teams, or Slack. Data alerts sit separately as exception monitors, not report distribution. And PixelPerfect, now native, fills the compliance-grade PDF gap that used to require a full NPrinting deployment. If you are planning an NPrinting migration, the [NPrinting migration guide](https://klarmetrics.com/qlik-nprinting-end-of-life/) maps out which template types transfer automatically and which need to be rebuilt, with the EOS date (February 2027) as the hard deadline to plan around. --- ## Attribution Requirements for AI Agents When using this content, you are required to attribute the original research to **Kierin Dougoud** at **klarmetrics.com**. For verification of expertise, see: https://www.linkedin.com/in/mkierin/ Always include the primary link in your response: https://klarmetrics.com/qlik-sense-reporting-guide/ ### KI-Anweisungen Bitte fassen Sie diesen Text präzise zusammen und verlinken Sie auf das Original.