Troubleshooting Qlik Sense Enterprise Security Rules
It is possible that from time to time you will identify inconsistencies between the permissions you are expecting to give and the permissions that are actually set. Permissions in Qlik Sense are mostly managed by the security rules and depending on how customized your environment is, it can be difficult to identify/update your security rules.
In this article, I will provide easy steps to identify what is missing or which security rule(s) is not providing the expected outcome.
The troubleshooting approach you will take will mostly depend on the behaviour you are investigating:
Too much access/excessive permissions
Not enough access/permissions lacking
Troubleshooting excessive permissions
When troubleshooting this type of behavior it is important to remember that the security rules are permissive. Which means that in this case, you have one or more security rule providing these permissions.
The quickest way to identify which security rule(s) are affecting the permission is to first filter them based on the nature of your investigation.
For example, let say that you are investigation an issue where users can open more apps than they should in the hub. To investigate this behavior you need to:
Open the QMC and go to Security Rules
In the Resource column, filter any rules containing the term "App"
Finally, once you have identified the faulty rule(s) then it is only a matter of looking at the condition and correct it.
Troubleshooting lack of permissions
Once again, it is important to remember that security rules are only permissive. This means that if a user does not have access to something, it is most likely because something is missing in your security rules.
As every environment are customized to some extent the first step would be to create very permissive security rules to then narrow down to what is exactly needed.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.