On April 16th, 2024, Qlik is launching a highly anticipated capability: custom security roles.
What do custom security roles do?
Custom security roles introduce fine control of data export and access permissions within Qlik apps. This allows you to tailor permissions to your specific needs, enhancing data security and compliance.
The first delivery on April 16th includes the capability to control who can export content. Additional capabilities will be added soon after, such as who can create data connections, reports, and similar.
What does this mean for me?
As part of this update, the existing "has restricted view" space role will gain the ability to export data to Excel. This adjustment is in line with Qlik's capacity-based pricing model, ensuring basic users have essential tools.
If you do not wish for users with the "has restricted view" space role to be able to export data, you will need to edit the User Default roleto deny download for all users, and thencreate a custom rolethat allows if for specific users and groups.
Stay tuned for more information and resources leading up to the April 16th launch. We are excited about these enhancements and the value they will bring to your data management and security efforts within Qlik.
I'm on Qlik Cloud - my team recently identified a bug on UK Tenants whereby an owner of a Data Space cannot be changed via UI @Sonja_Bauernfeind is this something you are aware of?
A solution to achieve this is qlik-cli. I have my team looking into this in more detail.
Initial feedback from my team is that qlik-cli will solve this issue, but could also be used to provide insights on what you have asked, eg; seeing who is downloading what - might be worth you/team investigating this further...
@Sonja_Bauernfeind - this is fab news about the custom rules. As I understand it, the "has restricted view" is pretty much only used to limit data export, so is this role going away or will it serve another purpose? It seems to me it will be identical to "can view" after this change.
@timherron - With the current "restricted view" (and the new custom one you'll need to create) they are applied to User Space permission, not to a User itself, so this way you can tailor permissions per Space - so you just need to make sure your sensitive data Apps are in Spaces with these restricted permissions.
