Qlik Fix: Reviewing differences of App access permission in QlikView and Qlik Sense

[Andre_Sostizzo]

 This video is part of the Qlik Fix Video series. If you found this video useful, check out the other Qlik Fix Videos.

This video aims at explaining some of the key differences when managing App access permission in QlikView and Qlik Sense.

Here is a link to more information in the Support Knowledge Base:

Reviewing differences of App access permission in QlikView and Qlik Sense 

Video Transcript:

Hi and Welcome to Qlik Fix
This video aims at explaining some of the key differences when managing App access permission in QlikView and Qlik Sense.
One of the Key differences between QlikView and Qlik Sense with respect to app access management is the concept of Streams and use of Security Rules in Qlik Sense.
In QlikView, authorization to Documents are setup for each file individually, whether using NTFS or DMS type of authorization.
If no Publisher is used, the same permissions can be applied to multiple files stored in specific directories by using NTFS permission inheritance.
In Qlik Sense, permissions are not set on a per app basis in the App's binary file. Only the Qlik Sense service account needs full access to these files.
Instead, Authorization is controlled by Security Rules which are stored in the Qlik Sense database.
Note that permission to Apps in Qlik Sense can also be setup in a individual basis using security rules.
Here's an example where the Resource filter contains the specific App ID, and permissions are granted to a specific Active Directory security group called Group0 which contains User1 and User3.
However, this is not the method suggested by the App publishing workflow in Qlik Sense.
"Streams" are used in order to publish Apps, collaborate with other developers, and make App changes public for user consumption.
When creating a Stream, one of the steps is to create and associate a new Security Rule.
This new security rule will state authorization details such as who may read, edit, or performed other tasks within the Stream.
Multiple security rules may be created for the Stream in order to provide different level of access to different users.
The rules that currently apply to Specific streams can be visualized by accessing the User access tab. Then double clicking on the Access level for the User. The same can be done under Apps.
Here we see the rule that sets all App objects associated with a specific stream to visible as long as the user has Read access to the specific stream.
As far as for providing anonymous access to apps, a key difference is that the account IQVS_servername needed in the QlikView is not required in the Qlik Sense environment.
Anonymous App access in Qlik Sense requires that either a "Login Access pass rule" or "Analyzer Capacity rule" such as this one is configured for Anonymous users.
The Everyone Stream allows access and Read permissions for Anonymous users by default. However, a new stream designated only for Anonymous can be created with the same condition.
Note that in Qlik Sense SaaS a similar app development and publishing workflow exists with the use of Spaces. For more information please refer to Qlik Sense Business and SaaS documentation.
Thanks for watching!

Attached is a downloadable .mp4 video file for those who cannot view YouTube videos.

#QlikSupport