Extending the Power of Qlik Sense with Rules

[Bjorn_Wedbratt]

The Qlik Sense system includes an attribute-based security rules engine that uses rules as expressions to evaluate what type of access users should be granted for a resource.

This article provides a collection of resources to help you get the best out of them.

All about Security Rules: On Qlik Help, we document our Security Rule concepts and how to be begin using them. 

Collection of Specific Rule Scenarios: See this article for a collection of Security Rule examples. Find more examples in our Qlik Community!

Extending the Power of Qlik Sense with Rules Webinar: In this webinar, we will discuss how rules work, the best practices, as well as giving you a live demonstration and a breakdown of some common challenges. 

See the video here: 

Q&A - Extending the Power of Qlik Sense with Rules

Q: Is it possible to hide Reload Now but keep Create new reload task function? Both actions have only one Resource filter - ReloadTasks_* .
A: No, this is not possible. Reload Now just is the right to create a reload task. The downside to the reload now functionality is that is created a manually triggered task which can clutter things up.
 
Q: is there a way to control field access via rules?
A: No, Security Rules won’t solve that scenario. The OMIT section access field would be the way to accomplish this: https://help.qlik.com/en-US/sense/April2018/Subsystems/Hub/Content/Scripting/Security/manage-securit...
 
 
Q: Is it poosible to create a rule to give access to an app that drives a mashup, yet not see the app in a stream?
A: Sure. This would be the style of approach: https://community.qlik.com/thread/292889
 
Q:  Hi, is it possible to just show Data Model Viewer?  And if there is omit column applied, would it be hidden in the model viewer?  Thanks.
A: No, this is not possible. Both the Data Model Viewer and Data Load Editor present when the user has App update rights.

Q:  You mentioned "sub stream" earlier. What's a sub stream?
A: There isn’t a single term for this, it’s just what I call it. But the concept is that there are exclusions in the Stream rule whereby providing a user access to a stream does not necessarily provide access to all apps in that stream. Like the Restricted exclusion section of the demo.