Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
I am wondering about Qlik Sense security.
1. When I installed Qlik Sense, I installed it using the Windows administrator account.
This account can access QMC and HUB.
However, I don't want to manage Qlik Sense with this account.
Is there a way to prevent the admin account I was installing from accessing QMC, HUB?
2. Is there any way that other users can't see the script I made?
you have to make some changes in Qsense QMC level
No, you don't need Section Access to manage this. Section access is a security layer used on applications to decide which data that is to be shown to which user.
Make sure that you have a Qlik root admin account. Using that admin account you can enter QMC and remove any admin role (like 'RootAdmim') that the service account user have and adjust any custom security rules that you made giving the service account additional authority in the Qlik Sense environment.
You should however be careful of revoking Windows admin rights to the user. It is possible to some limitations, but then read up on the instructions found in the installation documentation.
you have to make some changes in Qsense QMC level
Thank you for your help.
You meaning... to manage the account installed by QMC and the account of QlikSense Admin separately, right?
So I don't need to use it as 'Section Access'?
No, you don't need Section Access to manage this. Section access is a security layer used on applications to decide which data that is to be shown to which user.
Make sure that you have a Qlik root admin account. Using that admin account you can enter QMC and remove any admin role (like 'RootAdmim') that the service account user have and adjust any custom security rules that you made giving the service account additional authority in the Qlik Sense environment.
You should however be careful of revoking Windows admin rights to the user. It is possible to some limitations, but then read up on the instructions found in the installation documentation.