Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Everyone,
I have a table in Qlik Sense with some sensitive columns in it and I don't want to show these columns to everyone, lets say I want only one user to see the columns. I don't mind if there is a way that I create 2 tables one with limited columns and the other with full columns and set the full one to only specific user (and not be shown to others).
I also don't mind hiding the table in Qlik Sense, calling it in NPrinting and sending it, if the above is not possible.
I searched on the community for this, but I couldn't find something up-to-date related to this case (if there is such a thing please share the link)
Thanks in advance.
Security should be handled in the script, as mentioned in previous posts. Even if you block access to a table (and there's no easy way to do this), the user can still see the underlying values, for example by creating their own version of the table using Insight Manager, via duplication, or by viewing the underlying field values in the Selections screen.
If you want to try for "Security through obscurity", you can use a show/hide container and hide the table based on whatever rule you want, e.g. using the OSUser() function. This isn't actually security, though.
Look to the link Ahidhar sent and specially to the OMIT keyword. This should do the trick.
From what I studied in Section Access you have to provide all users and then give specific access to specific objects.
what if I don't know how many users are accessing the report and I don't want to change any security stuff, I just want to add a new table and just assign it to one person and that's it. Is there something like that?
Security should be handled in the script, as mentioned in previous posts. Even if you block access to a table (and there's no easy way to do this), the user can still see the underlying values, for example by creating their own version of the table using Insight Manager, via duplication, or by viewing the underlying field values in the Selections screen.
If you want to try for "Security through obscurity", you can use a show/hide container and hide the table based on whatever rule you want, e.g. using the OSUser() function. This isn't actually security, though.