QlikView Security Mechanisms

QlikView provides two primary methods for establishing security mechanisms:

Built-in Security Mechanisms in QlikView Document Script

QlikView allows security mechanisms to be integrated into the QlikView document script. These mechanisms include:

• Authentication: QlikView can authenticate users either through the Windows operating system, by prompting for a User ID and Password, or by using the QlikView license key as a simple authentication method.
• Authorization: QlikView can handle authorization itself by using a security table built into the script. The security table assigns access levels to users or groups, such as ADMIN or USER, to control their privileges within the document.

Security Mechanisms through QlikView Publisher

QlikView Publisher can also be used to set up security mechanisms. When QlikView Publisher is used, each QlikView file is split into several files, each containing data specific to a user or user group. These files are stored in folders with the appropriate OS security settings. In this scenario, the operating system handles authentication and authorization. However, it’s important to note that there is no built-in security within the downloaded file itself.

Sources

• QlikView Help: Security
• QlikView Help: Authorization
• Qlik Community: How would we give the security to the Qlkview Application plz

FAQs

How many ways can QlikView set up security mechanisms?

QlikView provides two primary methods for establishing security mechanisms: built-in security mechanisms in the QlikView document script and security mechanisms through QlikView Publisher.

What authentication methods does QlikView support?

QlikView supports authentication through the Windows operating system, by prompting for a User ID and Password, or by using the QlikView license key as a simple authentication method.

How does QlikView handle authorization?

QlikView can handle authorization itself by using a security table built into the script. The security table assigns access levels to users or groups, such as ADMIN or USER, to control their privileges within the document.

What is the advantage of using QlikView Publisher for security?

QlikView Publisher allows for more granular control over security by splitting each QlikView file into several files, each containing data specific to a user or user group. These files are stored in folders with the appropriate OS security settings, giving the operating system more control over authentication and authorization.

Is there any built-in security within downloaded QlikView files?

No, there is no built-in security within downloaded QlikView files when using QlikView Publisher. Additional measures may be needed to protect the file.

Can QlikView security mechanisms be used to restrict access to specific data within a document?

Yes, QlikView’s Section Access feature allows for dynamic data reduction, which can be used to restrict access to specific data based on the user’s credentials.

Can QlikView security mechanisms be used to prevent users from modifying the document layout or menu items?

Yes, QlikView’s Document Properties: Security page and Sheet Properties: Security page allow administrators to restrict access to certain menu items and prohibit changes in the layout.

What is the difference between ADMIN and USER access levels in QlikView?

The ADMIN access level allows users to make changes to the document, including modifying the security settings. The USER access level restricts users to viewing and interacting with the document, but they cannot make any changes.