Databases Reference
In-Depth Information
Security
Until now, we have focused our efforts on getting data into QlikView and presenting
it in dashboards, analyses, and reports. Our documents were open to anyone with
access to QlikView. As QlikView documents can contain huge volumes of sensitive
data, in a real world scenario, leaving your data unsecured might be a very
risky proposition.
In this chapter, we will focus on how we can secure our QlikView documents. We
will first look at how we can make parts of the script only accessible to a limited
group of developers. Next, we will see how we can ensure that only authorized users
have access to our document. We will finish this chapter by looking at how we can
set different permissions for authorized users and can limit which data a user can
interact with.
Specifically, in this chapter you will learn:
• How to create a hidden script that is only accessible to a select group of
developers
• How to allow only authorized users to open your document
• How to limit what a user can do and see within your document
Time to start locking things down!
Hidden script
When QlikView script is being executed, the results of the actions are written to
the
Script Execution Progress
window (and, if enabled, the
log
file). While this is
a very useful feature to see what happened during reload, sometimes you do not
want certain things (for example, login credentials) to be visible to everyone. In fact,
sometimes you do not even want all developers to have access to the entire script.
This is where the
hidden script
comes into play.
