Restricting confidential data field for app developer which is accessible to users

[chaorenzhu]

Hi, I came across this problem where there are some confidential data fields, that should not be accessible to app developer but when published to users, can be seen be users. Let's say there are 3 data fields needed: customer id, customer name, and sales amount. In the load script, the app developer reads all 3 data fields, including customer name which is confidential to them, through the ODBC connection, but they could not view the values of the customer names; while the dashboard users can actually view the customer names. Can you kindly advise if this is possible for Qlik Sense? Thanks.

[rubenmarin]

Hi, maybe there are other ways but when we needed to do something similar we create qvds removing or scrambling the confidential data, and these are the qvds used by the developers, they (we) don't have access to all the data, only when the app is published it's reloaded with all the data.

If you have a development server it's easier because each server has it's qvds (with or without confidential data), if there is only one server you can work with variables or app name or rest connections to detect when the app is published and use the data connection.

[chaorenzhu]

Thanks @rubenmarin. We're using Qlik Sense Enterprise SaaS, any workaround idea?