Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Dear All,
Does any body have an idea of 'SUPERUSER' usage for 'Access' field in section access ? if so could you please expose it with an example.
Thanks,
Kiran Kumar
Hi Kiran,
As far as I am aware USER and ADMIN are the only valid values for the ACCESS column in Section Access.
This has a use in QlikView, as an ADMIN user can get to additional settings menus which users can not, it does not change data access in any way (except an ADMIN can potentially change the script to grant themselves rights).
In Sense the ACCESS column serves no purpose, as all admin type permissions are set through the QMC with security rules. It therefore stands to reason that it could be ignored and any value can be placed there. Try putting in a random word and see if it still works.
The only reason for it being there AFAIK is so that script from QlikView doesn't break when ported to Sense.
Steve
Super User for will be ADMIN under Access column; Rest all the columns will be have * for full access.
ACCESSUSERIDPASSWORDEMPLOYEEID
ADMIN | SUPERUSER | What Ever | * |
Hi Hirsh,
Thanks for the update but I have seen SUPERUSER used as a value for 'ACCESS' keyword, and for now it is working similar to 'ADMIN' value but it has more usage as per the people whom I have discussed, but I couldn't get any docs in Qlik community exposing the real usage of it.
Regards,
Kiran Kumar
Hi Kiran,
As far as I am aware USER and ADMIN are the only valid values for the ACCESS column in Section Access.
This has a use in QlikView, as an ADMIN user can get to additional settings menus which users can not, it does not change data access in any way (except an ADMIN can potentially change the script to grant themselves rights).
In Sense the ACCESS column serves no purpose, as all admin type permissions are set through the QMC with security rules. It therefore stands to reason that it could be ignored and any value can be placed there. Try putting in a random word and see if it still works.
The only reason for it being there AFAIK is so that script from QlikView doesn't break when ported to Sense.
Steve
Hi Steve,
Thanks for the information, I have to hope for the same, will provide an update if I get any information from the architects who actually included this in the script.
Regards,
Kiran Kumar