User accounts

In order to successfully install and deploy Qlik Sense you must set up some user accounts before you start your Qlik Sense installation.

Windows user accounts are created and configured using your Windows server administration tools.

If you choose to manually install and configure your PostgreSQL repository database, users are created and configured using your PostgreSQL database administration tools. If you choose to have Qlik Sense install the repository database for you, the Qlik Sense setup wizard will create the users during installation.

The following are the users that you may need to create before you install Qlik Sense:

  • Windows Qlik Sense services administrator
  • Windows Qlik Sense services user that is not an administrator
  • PostgreSQL database superuser
  • Qlik Sense Repository Database administrator

You must create the required Windows user accounts before you install Qlik Sense because you are prompted to enter them during the installation. If you choose to install as a Windows local administrator and wish to change to a Windows dedicated Qlik Sense service user after installation, see Changing the user account to run Qlik Sense services.

When you create your Windows user accounts you must set a password for each one. Windows user account passwords may expire in accordance with the Windows domain security rules settings. If you do not update the passwords for each Windows service setting, the services will stop working. To avoid this, you can select the Password never expires check box in the Windows user profile, if your security protocol allows it.

Windows Qlik Sense services administrator

We recommend that you use a dedicated Windows user account to run the Qlik Sense services. If your dedicated Windows Qlik Sense services user is an administrator, you can login as that user to install Qlik Sense. If your dedicated Windows Qlik Sense services user is not a local administrator, you must use an administrator account to install Qlik Sense.

Windows Qlik Sense services user that is not an administrator

If you wish to use a dedicated Windows user account that is not an administrator to run the Qlik Sense services, you must create that account before you install Qlik Sense. The Windows Qlik Sense services user runs the following services:

  • Qlik Sense Repository Service
  • Qlik Sense Proxy Service
  • Qlik Sense Engine Service
  • Qlik Sense Scheduler Service
  • Qlik Sense Printing Service
  • Qlik Sense Service Dispatcher

For more information about services, see Services.

The Windows Qlik Sense services user that is not an administrator must meet the following requirements:

  • Member of the Qlik Sense Service Users and Performance Monitor Users groups.

    You add the Windows Qlik Sense services user that is not an administrator to these groups after you install Qlik Sense.

  • Only used for Qlik Sense Windows services. This is necessary to avoid conflicts with other Windows services in the same computer.

PostgreSQL database superuser

The PostgreSQL database superuser is a role that bypasses all permission checks, except the right to log in. It is not a Windows, or Qlik Sense user, it is a PostgreSQL user configured in the repository database.

If you choose to install the PostgreSQL database manually, you are prompted to create a PostgreSQL database superuser and password during installation. That user ID and password are used to connect your PostgreSQL database. For details about creating users with the PostgreSQL administration tools, see Installing and configuring PostgreSQL.

If you choose to install the Qlik Sense Repository Database locally during the Qlik Sense installation, the PostgreSQL installation is done automatically.

Note: When you install Qlik Sense, if you select the Install local database option, the QSR, SenseServices, and QSMQ databases are created automatically. These databases also share the same PostgreSQL login role. For more information, see Installing and configuring PostgreSQL

Qlik Sense Repository Database administrator

The Qlik Sense Repository Database administrator role has full access to the Qlik Sense Repository Database that contains all configuration data for the Qlik Sense site. It is not a Windows, or Qlik Sense user, it is a PostgreSQL user configured in the repository database.

If you choose to install PostgreSQL manually, the Qlik Sense Repository Database administrator is also created manually using the PostgreSQL administration tools. For details about creating users with the PostgreSQL administration tools, see Installing and configuring PostgreSQL. You must enter the location of the Qlik Sense Repository Database and the login credentails for the Qlik Sense Repository Database administrator during the Qlik Sense setup on the Shared persistence database connections settings page.

If you choose to install the Qlik Sense Repository Database locally using the Qlik Sense setup, you are prompted to set a user name and password for the Qlik Sense Repository Database administrator during the setup.

You must keep that password for backup and restore activities. It may also be needed for support.

User accounts for the logging database

Two user accounts, which use PostgreSQL password authentication, are automatically created during Qlik Sense installation. User account qlogs_writer is used internally by the logging service to write to the database. In fact, this user owns the logging database QLogs. User account qlogs_reader is used by the monitoring apps to read from the database. There is also a user account called qlogs_users, which is basically a group. It does not have a password and cannot be used to access the database. It exists only for the purpose of managing network access to the PostgreSQL database.

The system administrator can change the passwords for these database users directly from PostgreSQL. The logging service must also be updated with the new passwords using the update or setup command.

 

 

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?