Home > Multi-tenant administration

Multi-tenant administration

Does this category apply to me? Skip it if your subscription includes one tenant. To check: admin console → Settings → look at the subscription / tenant-count entitlement, or confirm in My Qlik under your subscription. Single-tenant customers can ignore this entire category.

This category covers tasks that apply when an admin (or admin team) is responsible for more than one Qlik Cloud tenant under the same subscription. Typical scenarios documented by Qlik include:

• OEM, ISV, and Digital Native Business partners providing analytics to multiple end customers, where Qlik's product description requires a separate tenant per organization. (Single vs multiple tenants)
• Enterprise customers running Dev / Test / Acceptance / Production (DTAP) environments, multi-region deployments for performance, or extranet (corporate vs. external) separation. (Platform operations overview)
• Qlik Talend Cloud subscriptions purchased on or after July 22, 2025, which automatically create and link the Qlik Cloud and Talend Cloud tenants during setup. (Creating and configuring your tenant)

Qlik's guidance is that each end customer in an OEM or Enterprise external-use deployment should have its own Qlik Cloud tenant: putting multiple end customers into a single tenant exposes user names, email addresses, and IdP subject identifiers across customers. (Creating and configuring your tenant)

Note. Single-tenant cadenced tasks (sections in AI services, Asset management, Data integration, Governance, Identity and access, Licensing, System spot check, and Tenant configuration) still apply to each managed tenant individually.

Topics

• Subscription and entitlement sharing—Pooled user-license counts, value meters, tenant-count entitlement attributes.
• Identity providers across tenants—Same-IdP recommendation to prevent duplicate license assignment.
• OAuth client tiers—Tenant-, region-, and organization-level OAuth2 clients.
• Tenant lifecycle automation with Platform Operations—Provision, configure, hydrate, deploy, and decommission tenants programmatically.
• Multi-tenant monitoring—OEM Dashboard, Console Settings Collector, multi-tenant aggregation patterns.
• Cross-tenant data residency, deletion, and PII—Region selection, tenant inventory, retirement obligations.
• Multi-tenant cadenced tasks summary—Daily / weekly / monthly / quarterly / yearly multi-tenant cadence reference.