This section guides you through the process of setting up your Qlik Sense site after installing. You can configure the server to fit with your organization’s particular needs. Below are the common task most deployments will require.
Connecting Qlik Sense to your user directory
Qlik Sense has a range of methods for authenticating users. Windows authentication is the default method.
When a user connects to Qlik Sense for the first time a user record is created to identify that user. Once this record is created, the administrator can track the user’s activity and assign her a license and permissions.
Administrators can also connect to a user directory (for example, Active Directory or LDAP) to obtain further information about that user (such as user groups). The user information can be fetched in advance and then kept in sync with the user directory. This is optional but recommended since it will provide you with the best management experience.
Users need a license to open an app.
Your license is either based on access types, with professional access allocation as an option, or on tokens, with user access allocation as an option.
- Access types: you can allocate professional access and analyzer access. Depending on how you have licenses Qlik Sense, the distribution of the two access types is determined by the LEF file or by the signed key.
Token-based license: you can allocate user access and login access. The LEF determines the number of tokens that you can allocate to the two access types.
User-based licenses grant a predefined number of professional and analyzer access allocations. The distribution of the access types is determined by the LEF.
Qlik Sense offers a token-based system that allows the administrator to assign the most suitable license type to each user. Licenses can be allocated on an individual basis or automatically by using rules to define who is allowed to obtain a license, for example, all users in a specific department.
Configuring the monitoring apps
All installations of Qlik Sense (single node and multi-node) require configuration of the monitoring apps for them to work properly.
Qlik Sense deploys securely by default when it is installed. It uses self-sign certificates to ensure that data is transferred to users in a secure way. When users access the system they by default receive a warning that the certificate used by the site is not trusted. The user can then accept the certificate and proceed to use Qlik Sense securely.
There are two options to prevent the warning; one is to use a trusted certificate from either a trusted provider or an internal corporate source. The other option is to run the site using HTTP only. Both options are available as settings on the Qlik Sense Proxy Service (QPS).
Regardless of which option you choose, the services in Qlik Sense always use encryption when communicating.
Creating and opening apps
To create and open apps on the server users must browse to the Qlik Sense hub using their web browser. The hub lists two areas: Work contains the apps belonging to the user who has logged in, and Streams contains the other apps the user has access to. After the installation the administrators see two built-in monitoring apps, while all other users do not see any apps. Click on an existing app to open it. To create a new app, click Create new app.
Working with streams, apps and publishing
A stream is a way to group together apps that have similar permissions. Once an app has been created, an administrator can publish it to a stream. The app then becomes visible to users who have access to that stream. Apps, streams and publishing are managed in the Qlik Management Console (QMC).