[Home](https://help.qlik.com/en-US/cloud-admin-playbook/Content/home.htm) > [Tooling appendix](https://help.qlik.com/en-US/cloud-admin-playbook/Content/tooling_appendix.htm) > Monitoring Apps Deployer

# Qlik Cloud Monitoring Apps Deployer

**Type:** Qlik Automate template

**Support model:** **Installer automation supported by Qlik Support.** Apps it installs are community-supported (with the exception of the Data Capacity Reporting App, which is fully Qlik-supported).

**Subscription model:** All

**Roles:** Tenant Admin (TA)

**Last verified:** 2026-05

|  | Initial | Recurring |
| --- | --- | --- |
| **Estimated time** | 1 hr | 5 min weekly or monthly |

**Benefits:**

* Set-and-forget install and upgrade for the community monitoring apps
* Automated API key rotation for the data connection
* Automatic detection of installed app versions via tags

***

## Goal

> **First-time orientation.** **Qlik Automate** is the no-code automation runtime included in every Qlik Cloud tenant—open it from the activity-center switcher in the top-left of **the hub** (the end-user landing page at `https://<tenant>.<region>.qlikcloud.com`, distinct from the admin console at `…/console`). A **template** in Qlik Automate is a prebuilt automation you import into the tenant, configure with your own variables, and run on demand or on a schedule.

A

> set-and-forget

install of the community-maintained monitoring apps is provided by the **Qlik Cloud Monitoring Apps Deployer** template in Qlik Automate. As of the December 4, 2025 update, the unified deployer replaces the original separate installer / API-key rotator templates; per the workflow guide,

> disable or delete any existing installers, and create a new automation.

Source: [Qlik Cloud Monitoring Apps Workflow Guide](https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Monitoring-Apps-Workflow-Guide/ta-p/2134140).

> The **Qlik Cloud Monitoring Apps** project is community-supported. Qlik doesn't support these apps with the exception of the Data Capacity Reporting App.

## What the deployer does

* Installs / upgrades all or a subset of monitoring apps from Qlik's [qlik-cloud-monitoring-apps](https://github.com/qlik-oss/qlik-cloud-monitoring-apps) OSS repository (Access Evaluator, Answers Analyzer, App Analyzer, Automation Analyzer, Entitlement Analyzer, Reload Analyzer, Report Analyzer). The **Console Settings Collector** isn't a deployer target—it ships alongside the OEM Dashboard releases.
* Creates required spaces (shared / managed) and the analytics REST connection.
* Creates / rotates the API key for the data connection.
* Creates a daily reload schedule and (optionally) reloads apps after install.
* Tags installed apps with `QCMA - {appName}` and `QCMA - {version}` so subsequent runs detect them; **manually installed apps are not detected** and will be installed side-by-side.
* Supports both user-based and capacity-based subscriptions (subject to per-app compatibility—see the [applications matrix in the OSS repo](https://github.com/qlik-oss/qlik-cloud-monitoring-apps?tab=readme-ov-file#applications)).

## Configuration variables

Set these variables before the first run:

* `configuredMonitoringApps`
* `refreshConnectorCredentials`
* `reloadNow`
* `reloadScheduleHour`
* `sharedSpaceName`
* `managedSpaceName`
* `versionsToKeep`

## Recommended cadence

| Frequency | Why |
| --- | --- |
| Weekly or monthly run | Picks up new app versions; refreshes API key when `refreshConnectorCredentials = true`. |
| Combined with Qlik Data Alerts | Notifies admins when a new monitoring-app version is published. |

## Tasks

| Task | TA | AA | DA | AuA |
| --- | --- | --- | --- | --- |
| Run the deployer template on a weekly or monthly schedule to keep apps current | ✓ |  |  |  |
| Subscribe to **Qlik Data Alerts** on the deployer to be notified when a new monitoring-app version is available | ✓ |  |  |  |

## Gotchas

* **The deployer only manages apps that bear the `QCMA - {appName}` and `QCMA - {version}` tags.** Any monitoring apps installed manually before the deployer was first run won't be detected; the deployer will install fresh side-by-side copies. Plan to retire the manually-installed copies after migration.

## Roles for running and consuming

| Activity | Role(s) |
| --- | --- |
| Run / schedule the deployer template | **Tenant Admin with the `Manage API keys` permission**—required so the automation can create spaces, data connections, schedules, and the API key. (`Manage API keys` replaced the deprecated **Developer** role on January 26, 2026.) |
| Review the resulting **Monitoring** managed space and consume the apps | **Tenant Admin**, **Analytics Admin**, and any user with the relevant space role. (**Audit Admin** is required separately to inspect raw Qlik Answers conversation transcripts in the audit UI—not to consume the Answers Analyzer dashboard.) |

## References

* [Qlik Cloud Monitoring Apps Workflow Guide](https://community.qlik.com/t5/Official-Support-Articles/Qlik-Cloud-Monitoring-Apps-Workflow-Guide/ta-p/2134140)
* [qlik-cloud-monitoring-apps (OSS repo)](https://github.com/qlik-oss/qlik-cloud-monitoring-apps)
* [The Qlik Sense Monitoring Applications for Cloud and On Premise](https://community.qlik.com/t5/Official-Support-Articles/The-Qlik-Sense-Monitoring-Applications-for-Cloud-and-On-Premise/ta-p/1822454)
* [All templates (Qlik Help)](https://help.qlik.com/en-US/cloud-services/Subsystems/Hub/Content/Sense_QlikAutomation/introduction/template-list.htm)

**Tags:** `#monthly` `#tooling` `#monitoring_apps` `#deployer` `#qlik_automate`