Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Qlik experts,
In our organisation we work with very sensitive data. Our department is responsible for handling this data and we have all sorts of regulations concerning the storage and distribution of the data.
We have several users that are able to create their own apps. We now noticed that some users also use their own Excel files in some of their apps, without us having any governance over the data. Because we are responsible for all the data in Qlik, we want to disable this functionality.
Basically, I want these users to not be able to upload their own data to Qlik, such as the button as shown below. Is there a security rule that allows this? I've been looking but haven't been able to find it.
(Picture is in Dutch, but this is the button when you create a new app without any data in it).
I think you can disable this via the QMC.
for example give some users access to upload data and others not.
please take a look at this posts:
https://community.qlik.com/t5/New-to-Qlik-Sense/Turn-off-CSV-uploads/td-p/1745777
I don't know if this is possible, but even if it is, I don't think it'll achieve what you want. If you block the option to use files, users can still use Inline Load to load the data within the file manually. If the issue is governance, I'd suggest preventing people from publishing apps into public spaces and instead having them work through your department, who would confirm the validity of the data before publishing the app.
I think you can disable this via the QMC.
for example give some users access to upload data and others not.
please take a look at this posts:
https://community.qlik.com/t5/New-to-Qlik-Sense/Turn-off-CSV-uploads/td-p/1745777
You are right, the users could still upload it using an Inline Load or manual insert. The functionality of being able to publish apps themselves is very important to them though. We're looking for a middle ground. Thanks for your input!
This was it! I actually saw this security rule and disabled it, but didn't test it on a non-admin user account. Thanks!