Skip to main content Skip to complementary content

Section access

You can configure section access for Qlik NPrinting when generating reports from QlikView documents or Qlik Sense apps. Section access support is handled differently for local connections, and for server and cluster connections.

Connecting to QlikView documents with section access

Create a new connection to a local document

Do the following:

  1. Open the Apps drop-down list, and then select Connections.
  2. Click Create connection.
  3. Enter a Name for the connections.
  4. Enter a description (optional).
  5. Select an App from the drop-down list.
  6. Ensure the Source is set to QlikView.
  7. Select Local in the document Type.
  8. Enter the complete path to reach the .qvw in the Document path field.
  9. Ensure the Connection requires authentication check box is selected.
  10. Enter the Username and Password.

  11. Click Create.

Prerequisites for QlikView Server and QlikView Cluster connections

To generate reports using QlikView Server or QlikView Cluster connections, the following are required:

  • Access to at least one QlikView Server.
  • The Windows user that runs the Qlik NPrinting Engine Windows service must belong to the QlikView Administrators Windows group on the QlikView Server computer.
  • To configure Qlik NPrinting for NTFS authorization, it must be configured in the Qlik Management Console. This means that the Windows operating system controls the file (document) access for users and groups through the NTFS security settings.
  • To configure Qlik NPrinting for DMS authorization QlikView controlled file access, see JWT authentication.

If you are using section access as well, the following are also required:

  • Connections must be configured to use server authentication.
  • A domain account must be configured in user settings, independent of the authentication type enabled in the Qlik NPrinting general settings.

Create a new connection to a server document

Do the following:

  1. Open the Apps drop-down list, and then select Connections.
  2. Click Create connection.
  3. Enter a Name for the connections.
  4. Enter a description (optional).
  5. Select an App from the drop-down list.
  6. Ensure the Source is set to QlikView.
  7. Select Server in the document Type.
  8. Enter the complete path to reach the .qvp in the qvp:// field.
  9. Ensure the Connection requires authentication check box is selected
  10. Select Server authentication and enter the Identity.
  11. Click Create.

Create a new connection to a cluster document

Do the following:

  1. Open the Apps drop-down list, and then select Connections.
  2. Click Create connection.
  3. Enter a Name for the connections.
  4. Enter a description (optional).
  5. Select an App from the drop-down list.
  6. Ensure the Source is set to QlikView.
  7. Select Cluster in the document Type
  8. Enter the cluster Address, Cluster ID and Document name.

    The cluster address and ID can be found in the Qlik Management Console under System > Setup. The cluster address is in the Management service > Summary tab. The cluster ID can be found by selecting the QVWS server under QlikView Web Servers, and the ID is in the Name field of the General tab.

  9. Ensure the Connection requires authentication check box is selected.
  10. Enter the server authentication Identity.

  11. Click Create.

User configuration

Do the following:

  1. Open the Admin drop-down list, and then select Users.
  2. Click the Name of the user that needs to receive reports with section access applied.
  3. Configure the Domain account field with a valid user that has access to the document.

  4. Click Save.

Connecting to Qlik Sense app with section access

Do the following:

  1. Create a new connection to a Qlik Sense app as described in Creating connections or open an existing one.
  2. Flag the check box Apply user section access for reports to apply section access for the selected Identity.
  3. Click Create or Save to confirm.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!