Vote for your favorite Qlik product ideas and add your own suggestions.
Unlike Qlikview, Qlik Sense still displays published applications to users who cannot open them due to section access security.
It would be preferable to not display these applications in the Hub.
Unpublished applications should still be visible to the owner when access is denied.
Section access currently is used for data reduction. For most of our users, the apps co-exist in streams where some apps apply to a user, and others don't. There is a convoluted way to set this up from the server-side using the configuration method but makes way more sense to have this function baked into section access itself or to have a stream level section access so rather than reducing data, we can reduce the number of apps available for the user to interact with.
Hi @Peter_Adams thank you for sharing the idea with us. This is actually something which we do have listed on our backlog improvement road map. It's not decided yet if we do it and how but I'll update the idea as soon as I know which will be early next year.
Any update on this Idea?
Also, @Peter_Adams can you elaborate more on the idea?
Do you mean that if a user doesn't have access to an app based on the section access, the app shouldn't be visible to the user?
If this is possible, that will be great.
Yes, that is the goal.
PLEASE MAKE THIS A THING! I support six enterprise clients and most of them want this as a feature. having to do app by app security or make ton of streams to hide apps is nuts.
@Peter_Adams and @Thomas_Hopp
Any update on this idea?When can we expect to have this functionality in Qlik Sense?
yes this would be a great addition in Qlik Sense SaaS too
Following. Please make this an option, i have 2 clients that refuse to migrate because of this one silly thing.
this "flaw" constantly gets bashed by our customers,it would be very nice to deliver this feature soon.
@Peter_Adams @philipp_kunz @panderson @rob_insley @@
Do we have an update on this ?
We also need this functionality in order to reduce Admin overhead .
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.