Skip to main content Skip to complementary content

Configuring Qlik Sense to allow users to publish a link to shared content

You must create a Qlik Sense security rule and configure the Qlik Sense repository to allow QlikView to publish links on the Qlik Sense hub.

Adding a shared content security rule

Enable shared content by creating a new security rule in the QMC.

Do the following:

  1. Open the QMC: https://<QPS server name>/qmc

  2. In the QMC, open the Security rules.

  3. Click Create new at the bottom of the page.

  4. In the Identification section, add a name and rule description. You can use the suggestions in the following table.
    Identification fields and values suggestions
    FieldValue
    NameSharedContentCreate-AllUsersFromUserGroupName
    DescriptionAll users from the domain UserGroupName are allowed to create shared content
  5. In the Basic section, type SharedContent_* as a Resource filter.

  6. Select the Create action and ensure that the Read action is cleared.

  7. Complete the action rule definition using the values in the following image by replacing UserGroupName with the name of your authentication user group.

    The action rule definition interface

  8. (Optional) If you want all authenticated users to be allowed to share QlikView content, type !user.IsAnonymous() in the Conditions box.

  9. Click Apply.

The security rule has now been added to the QMC for authenticated users.

Enabling shared content in the Qlik Sense repository

To enable shared content in the Qlik Sense repository, you must update the configuration file. By default, the Repository.exe.config file can be found in C:\Program Files\Qlik\Sense\Repository\ on your Qlik Sense machine. Edit the configuration file and change the value of the SharedContentEnabled key to true. Restart the Qlik Sense Repository Service using the Windows Services application to enable this new configuration.

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!