Skip to main content Skip to complementary content

Home > Getting started

Getting started as a new Qlik Cloud admin

Last updated: 11/3/2026

If you've just inherited a Qlik Cloud tenant—or you're the new admin alongside an existing team—work through this page first. It sequences the most important orientation reading and the most load-bearing operational checks. Once you've completed the Day 1 / Week 1 / Month 1 list below, return to the Home page cadence table for the full recurring playbook.

Keep the Glossary open while reading. Qlik-specific terms (spaces, value meters, entitlements, gateways, Discovery Agent, recovery URL) appear before they can be redefined inline; the glossary is the canonical reference for each.


Day 1—orient

Step What to do
1 Read About this playbook—especially the Subscription model section. Identify whether your tenant is user-based or capacity-based (and whether it has the Anonymous Access subscription). The rest of the playbook depends on knowing this.
2 Read Administrator roles. Note which role(s) you hold today and who else holds Tenant Admin and Service Account Owner.
3 Open the Home dashboard in the admin console. The URL pattern is https://<tenant>.<region>.qlikcloud.com/console; the exact hostname is in your Qlik welcome email and in My Qlik. Note your tenant region and current value meters (see Monitor capacity consumption for the 80 / 90 / 100% action thresholds—Week 1 step 3 reinforces this).
4 Confirm who the Service Account Owner (SAO) is and that the mailbox originally used to create the tenant is still reachable—Qlik's IdP-recovery URL is bound to that mailbox, and Qlik Support can't restore IdP configuration without it. See Review SAO and IdP.

Week 1—verify resilience

Step What to do
1 Confirm there are at least two Tenant Admins (Qlik's recommended minimum for IdP-recovery resilience). Audit user lifecycle.
2 Read Monitor system events and walk through the admin console Events page once.
3 Read Monitor capacity consumption and confirm you understand which value meters apply to your subscription.
4 Inventory your Data Gateways (if any) and confirm each is Connected. Check gateway health.
5 Read Review release changes—pay attention to upcoming deprecation notices; some cutovers may already have run.

Month 1—establish the cadence

Step What to do
1 Deploy the Qlik Cloud Monitoring Apps Deployer—a Qlik Automate template that installs and updates the community-supported monitoring apps (Reload Analyzer, App Analyzer, Access Evaluator, etc.).
2 Walk the full cadence summary once. Schedule the daily, weekly, monthly, quarterly, and yearly tasks into your calendar / runbook.
3 Read Review SAO and IdP and Disaster recovery and BCP. Document your tenant's recovery URL and rehearsal plan.
4 If you operate more than one tenant under the same subscription, read Multi-tenant administration.
5 Familiarize yourself with the Tooling appendix—knowing which monitoring app surfaces which signal saves time during incidents.

How to use this playbook

Each topic page in the playbook follows a consistent format:

  • Cadence—Daily / Weekly / Monthly / Quarterly / Yearly.
  • Subscription model—Which subscription(s) the activity applies to.
  • Roles—Which administrator role(s) can perform the activity. See Administrator roles for the abbreviations (TA, AA, DA, AuA, SAO).
  • Estimated time—Initial is the time to learn and complete the activity the first time; Recurring is the time per subsequent occurrence at the listed cadence.
  • Benefits—Why this activity matters.
  • Goal—How to perform the activity, with links to official Qlik sources.
  • Tasks—A role-tagged checklist.
  • Gotchas (when applicable)—Surprising or edge-case behavior to watch for.
  • Automation helpers (when applicable)—Qlik Automate templates that reduce manual effort.
  • References—Underlying Qlik Help, qlik.dev, and Qlik Community links.
  • Tags—Cadence, category, and tooling tags for search and filtering.

See also

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 – please let us know!