Skip to main content Skip to complementary content

Creating a connection

To select and load data from the Qlik Web Storage Provider Connectors, you must have access credentials for the data source that you want to connect to. Once you create a connection and authenticate it with your access credentials, it is stored under Data connections in the Data load editor or Data manager.

Creating a data source connection

Data load editor

Do the following:

  1. Under Prepare, click Data load editor.
  2. Click on Create new connection.
  3. Select the connector.

Data manager

You can also create a data source connection by clicking Add data.

Do the following:

  1. Under Prepare, click Data manager.

    Click + or Add data.

  2. Select the connector.

Account properties

Credentials

Credentials are used to prove that a user is allowed to access the data in a connection.

There are two types of credentials that can be used when making a connection in Qlik Sense SaaS. If you leave the User defined credentials check box deselected, then only one set of credentials will be used for the connection. These credentials belong to the connection and will be used by anyone who can access it. For example, if the connection is in a shared space, every user in the space will be able to use these credentials. This one-to-one mapping is the default setting.

If you select User defined credentials, then every user who wants to access this connection will need to input their own credentials before selecting tables or loading data. These credentials belong to a user, not a connection. User defined credentials can be saved and used in multiple connections of the same connector type.

In the Data load editor, you can click the Primary key underneath the connection to edit your credentials. In the hub or Data manager, you can edit credentials by right-clicking on the connection and selecting Edit Credentials.

See which authentication type applies on each connector's page.

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!