topic Re: Best Practices for Managing Personal Sheets in Qlik Sense Apps in Management & Governance

Best Practices for Managing Personal Sheets in Qlik Sense Apps

Thomas_Hopp — Tue, 29 Jul 2025 14:25:45 GMT

The ability for users to create personal sheets in Qlik Sense is a powerful feature that supports self-service and flexible data exploration. However, in environments where governance and consistency matter, this capability needs to be carefully managed.

This document outlines one recommended approach to handling the use of personal sheets within a governed content workflow. While there are multiple ways to structure this, the approach described here aims to balance two requirements: enabling user-driven analytics and maintaining control over curated, production-ready content.

Read all about it in Qlik Cloud: Best Practices for Managing Personal Sheets in Qlik Sense Apps.

Re: Best Practices for Managing Personal Sheets in Qlik Sense Apps

Or — Tue, 29 Jul 2025 12:42:02 GMT

This is best practice? It sounds like a maintenance nightmare that takes up twice as much memory / disk space / etc...

If this is indeed Qlik's best practice, Qlik could stand to make it easier to implement by creating an app mirror - literally just a pointer to the same app but with its own location and server-side objects. This would prevent the need for double maintenance and make it a lot clearer on how this is meant to be handled, and would hopefully also prevent the need to load the app twice in disk/memory (depending on implementation).

Off to Ideation I go, I guess!

Re: Best Practices for Managing Personal Sheets in Qlik Sense Apps

JanJorissen — Tue, 29 Jul 2025 14:24:59 GMT

In case of disk space, you're absolutely right.

As for memory, depending on how many private sheets are in the app and the content, together with how many users are accessing the app, having a copy of the app can dramatically lower the footprint.

It is up to the SysAdmin to decide how many Engines an app can be load-balanced to. It makes sense to load balance the app where people experiment and add resource-heavy objects to a single node only, while the non-self service streamlined app is load balanced to multiple engines for the larger audience. It will contain the inherent risk of self-service to a single machine, and its consumption won't be multiplied over all available engines. There also won't be a high need for caching user-specific objects, potentially impacting app opening times globally. User cache is never generated together with the app cache; it happens when the app is opened by the user.

All that said, both applications will indeed need to be reloaded separately, and as you mentioned, it will use more disk space. It all depends on what is prioritized by the business. If a smooth and quick app performance for all (the many) users is the priority, self-service can likely compromise that proposition.
That's just my take.

Re: Best Practices for Managing Personal Sheets in Qlik Sense Apps

Or — Tue, 29 Jul 2025 17:39:16 GMT

Thanks for the input, @JanJorissen

I do think I'll still be heading over to ideation, because with this policy, it seems like it'd be a good idea for Qlik to add the option of a "Curated" and "Public" version of the same app. If both point at the same base app, you don't need two apps, double maintenance, double reloads, etc, but each would still have its own server-side objects such as public bookmarks and public sheets.

Not sure how much effort this entails, but given this is the recommended practice, it may be worthwhile to consider.