One of the ways Qlik Sense differs from QlikView is how it handles security for user access to resources and data.
Access to a resource — streams, apps, app objects, data connections — requires a security rule.
Simply put, a security rule allows a user to perform an action on a resource provided that the rule condition is true.
A user has no access to any resources unless a security rule grants access to a resource to perform an action.
A Qlik Sense security rule has a stream that contains various applications. Sheets and charts are objects within an application.
A security rule has four distinct elements: Resource filter, condition, operators, and actions.
A resource filter can be either App* or App_*. There is a subtle yet profound difference when you use * or _*.
App* means Apps and objects in the hierarchy.
App_* means only at the app level or resource type app.
Custom properties allow you to assign your own values to users and resources.
Once values are created and assigned, you can create a rule condition using @ symbol for the custom properties.
Example: If you create a custom property AppADGroup and add value finance, you can then create a rule condition to allow members of the AD group finance to access an app.
user.group = resource.@AppADGroup
You can not only use attributes from active directory, LDAP but also using custom properties to compare assigned attributes of a user against attributes assigned to resources to either grant or deny access.
If two Qlik Sense security rules overlap — if both rule conditions target the same users or resources — then the security rule that grants access will prevail.
So, it is always a good practice to audit your security rules to ensure proper access.
Both QlikView and Qlik Sense use Section Access for dynamic data reduction.
Section Access can perform both row and column level data reduction for a user or a group.
QlikView vs. Qlik Sense Section Access
You can use a QlikView Section Access script into a Qlik Sense application. However, due to subtle differences between how Section Access works in QlikView and Qlik Sense, you may have to tweak your script to make it work.