To audit changes in Qlik Cloud, you can use a combination of Qlik Cloud’s built-in activity log, tenant-level event tracking, and third-party ALM tooling to capture who changed what, when, and why. Qlik Cloud provides native logging for user actions and system events, but the depth of change tracking at the app level is limited without additional tooling. This article walks through what Qlik Cloud logs natively, how to track app-level changes, and how to close the gaps with a structured governance approach.
What does Qlik Cloud actually log by default?
Qlik Cloud logs user activity and system events at the tenant level by default. This includes actions such as user logins, app opens, space changes, permission updates, and data reloads. These events are accessible through the Activity Center in the Management Console and can be exported for external analysis or compliance reporting.
The built-in activity log captures a useful range of operational events, including:
- User authentication events (logins, logouts, failed attempts)
- App access and sharing actions
- Space membership changes and permission assignments
- Data reload triggers and outcomes
- App creation, duplication, and deletion
What the default log does not capture in detail is the content of changes made inside an app. If a developer modifies a chart, updates a load script, or adjusts a data model, those internal changes are not recorded at a granular level through native Qlik Cloud logging alone. For teams that need to track exactly what changed within an app across versions, this is a meaningful gap.
How do you track who changed what in a Qlik Cloud app?
Tracking who changed what inside a Qlik Cloud app requires version control or change management tooling layered on top of Qlik Cloud’s native capabilities. Qlik Cloud does not natively record field-level or object-level changes within an app, so identifying specific modifications relies on comparing app versions or using an external ALM solution that captures those differences.
In practice, teams that want meaningful change tracking typically follow one of these approaches:
- Manual version snapshots: Developers export and save app copies at key milestones, then compare them manually. This works at small scale but becomes error-prone as teams grow.
- Qlik Cloud spaces and promotion workflows: Using separate development, test, and production spaces creates a natural checkpoint structure, but does not automatically log what changed between promotions.
- ALM tooling with change tracking: External Application Lifecycle Management solutions can capture each change made to an app, link it to a user and timestamp, and generate a full audit trail that covers the internal structure of the app.
For regulated industries or teams with formal change management requirements, the first two approaches rarely meet compliance standards on their own. A structured process that records the author, the nature of the change, and the approval status is typically needed.
What’s the difference between an audit log and version control in Qlik Cloud?
An audit log records events that have already happened, while version control manages and preserves the state of an app at specific points in time so that changes can be compared, reversed, or approved before going live. Both serve governance purposes, but they answer different questions: an audit log tells you what happened, and version control tells you what changed and gives you the ability to act on it.
In the context of Qlik Cloud governance, the distinction matters in practice:
- Audit logs are useful for security reviews, compliance reporting, and investigating incidents. They answer “who did what and when?”
- Version control is useful for development workflows, testing, and rollback. It answers “what is different between this version and the last, and which version should be in production?”
Qlik Cloud provides audit logging natively through the Activity Center. Version control, in the traditional sense of comparing app content across iterations and managing promotion between environments, is not a built-in feature of Qlik Cloud and requires additional tooling or a disciplined manual process. Organizations that conflate the two often discover compliance gaps when an auditor asks not just what happened, but what specifically changed in the app and who approved it.
How can ALM tools fill the gaps in Qlik Cloud auditing?
ALM tools extend Qlik Cloud’s native auditing by adding structured version control, approval workflows, change tracking at the app level, and full lifecycle reporting. Where Qlik Cloud’s built-in logs capture user actions at the platform level, an ALM solution captures what changed inside the app, enforces a controlled promotion path, and produces an auditable record that satisfies compliance requirements.
Specifically, a well-implemented ALM solution for Qlik Cloud typically adds:
- App-level change tracking: Every modification to a Qlik Cloud app is recorded, linked to the user who made it, and stored as part of the app’s history.
- Lifecycle reporting: A full view of each app’s journey from development through testing to production, with timestamps and approval records at each stage.
- Approval gates: Changes must be reviewed and approved before they are promoted to a test or production environment, reducing the risk of unauthorized or untested changes reaching business users.
- Rollback capability: If a deployed version causes issues, teams can revert to a previous known-good state quickly and with a clear record of the rollback action.
- Data lineage visibility: Understanding how a change to a load script or data model propagates through downstream reports and dashboards, so the impact of any modification is visible before deployment.
Together, these capabilities transform Qlik Cloud change auditing from a reactive activity into a proactive, structured process that supports both operational efficiency and regulatory compliance.
When should organizations implement a formal change audit process?
Organizations should implement a formal change audit process for Qlik Cloud as soon as multiple people are contributing to the same BI environment, or when apps are being used to support business decisions that carry financial, operational, or regulatory consequences. At that point, the risk of untracked changes outweighs the effort of putting a structured process in place.
There are several clear signals that a formal process is overdue:
- Your team has experienced a situation where a production app broke and nobody could identify what changed or who changed it
- You operate in a regulated industry such as healthcare or financial services, where change documentation is a compliance requirement
- Multiple developers are working on the same apps without a clear handoff or review process
- Business users are reporting inconsistent results between dashboard versions
- Your organization is migrating from Qlik Sense on-premises to Qlik Cloud and needs to ensure governance continuity through the transition
Even outside regulated industries, the operational cost of uncontrolled changes accumulates quickly. Time spent diagnosing broken reports, reconciling conflicting app versions, or manually coordinating deployments across environments is time not spent on analysis. A formal audit process reduces that overhead and builds confidence across the business that BI outputs are reliable.
How PlatformManager helps with auditing changes in Qlik Cloud
We built PlatformManager specifically to close the governance and auditing gaps that Qlik Cloud teams encounter as their BI environments grow in complexity. Our BI Governance solution gives organizations the full change audit trail that native Qlik Cloud logging does not provide on its own.
Here is what we offer for Qlik Cloud change auditing:
- Full lifecycle reporting for every app, showing each change, who made it, and when
- Version control with comparison so teams can see exactly what changed between app versions before promoting to production
- Enforced approval workflows that ensure no change goes live without the right sign-off
- Data lineage insights to understand the downstream impact of any modification
- Compliance-ready audit trails that fully meet requirements such as HIPAA and Sarbanes-Oxley
- Support for multiple BI platforms from a single installation, including Qlik Cloud, Qlik Sense, QlikView, Power BI version control and governance, and SAP BusinessObjects
We are trusted by over 200 companies and supported by more than 30 Qlik partners. The best way to see the difference a structured audit process makes is to experience it directly. Start your free three-day trial and explore PlatformManager with full access to a cloud server, including a demo collection of apps and data.