Qlik Sense streams / Qlik Cloud shared and managed spaces

Streams and spaces to workspaces and apps in Power BI

Qlik separates authoring (personal and shared spaces) from consumption (managed spaces or streams). Power BI does the same with workspaces for building and Power BI apps for distributing to readers.

Partial / different approach Power BI service

Short answer: Shared space → a workspace where developers have Member or Contributor roles. Managed space or stream → a workspace published as a Power BI app, with readers given app access (optionally split into audiences). Personal space → My workspace (for drafts only).

What it does in Qlik

In Qlik Cloud, managed spaces have roles such as Consumer, Contributor and Publisher, and apps are published from a shared space into a managed one. Streams play the same role in client-managed Qlik Sense.

Qlik example

Qlik expression

// Shared space "Sales – Dev"  → develop apps
// Publish → Managed space "Sales" → consumers see published copy

Power BI equivalent

Mapping

Shared space → workspace Sales – Dev; roles Admin, Member, Contributor
Publish to managed space → Create app from the workspace, or use deployment pipelines (Dev → Test → Prod workspaces)
Managed space consumers → app audiences, or Viewer role on the Prod workspace
Space data connections → gateway connections and data source credentials on the semantic model

Gotchas and behaviour differences

Viewers who only have app access can't build new reports on the model unless you grant Build permission on the semantic model.
Readers need a Pro or PPU licence unless the workspace is on Premium/Fabric capacity (F64 or larger for free viewers). Check this before mapping Qlik "analyzer" users.
Section access in the app becomes RLS on the semantic model. Workspace Admins, Members and Contributors bypass RLS, so give test users Viewer.

Official documentation

Working in spaces (Qlik Help)
Roles in workspaces in Power BI (Microsoft Learn)
Publish an app in Power BI (Microsoft Learn)
Overview of deployment pipelines (Microsoft Learn)

Section Access; LOAD ACCESS, USER.EMAIL, REGION ...; Section Application; Section Access (data reduction) Section Access reduces data per user with a security table in the script. Power BI uses row-level security roles: DAX filters evaluated with the signed-in user's UPN, usually through a security table. OMIT maps to object-level security. Partial / different approach Master items: reusable dimensions, measures and visualizations Master items (master dimensions and measures) Qlik master items are governed, reusable expressions stored in the app. In Power BI the equivalent is a measure in the semantic model. Every measure is reusable by default. To share across reports, publish one semantic model and build thin reports on it. Partial / different approach Scheduled reloads, reload tasks and task chains Reload schedules and tasks A Qlik reload becomes a semantic model refresh in the Power BI service. On-premises sources need an on-premises data gateway. Chained tasks (load QVDs, then the app) become a Fabric Data Factory pipeline or an API-driven sequence. Partial / different approach

Spotted an error or a better pattern? QlikToDax is maintained by a working BI consultant; corrections are welcome via the About page. Last reviewed 2026-10-25.