Creating your workspace
Connecting to Qlik Cloud, defining address and language.
Registration has four steps.
The procedure is normally carried out by whoever administers Qlik Cloud. Access to the Management Console is a prerequisite of the second step.
1. Name and address
Enter the organisation's name and the workspace address, in the form
yourcompany.newhub.com. Availability is verified as you type.
The choice of address deserves attention. It is the link used across the organisation and it forms part of the credential registered in Qlik in the next step. Changing it afterwards requires updating that credential in Qlik.
2. Connecting to Qlik Cloud
The step takes place across two screens, Qlik Cloud's and NewHub's.
In Qlik Cloud, open Management Console → Settings → OAuth clients and create a client of type Web with the following configuration:
| Field | Value |
|---|---|
| Redirect URI | exactly the address displayed on the NewHub screen |
| Scopes | user_default and offline_access |
| Machine-to-Machine | allowed, with user impersonation |
| Authentication | by client secret |
Take note of the Client ID and the Client secret, which appear on the creation screen. The secret does not appear again after leaving the screen, so keep it in a safe place. Never share the Client secret with anyone outside your organisation: it grants access to all Qlik data that the user who created the client can access. Never share the Client secret with anyone outside your organisation: it grants access to all Qlik data that the user who created the client can access.
After creating, change the consent method to Trusted of the created OAuth client.
Back in NewHub, enter the Client ID and the Client secret and select Connect and verify. The confirmation displays your Qlik user name. The absence of that confirmation indicates a divergence in one of the five fields above.
The Redirect URI requires an exact match, character for character. If the workspace address is changed at the previous step, update the value in Qlik before proceeding. Qlik refuses the authentication and the error message references
redirect_uri.
3. Branding and language
Enter the logo and the workspace's default language. Both remain editable afterwards in the administration area, alongside colours and the remaining appearance settings.
The Terms of Use and the Privacy Policy are accepted at this step, once, by whoever creates the workspace. There is no per-member acceptance: users invited afterwards reach the portal directly.
4. Completion
Registration ends at the workspace address, already authenticated. Whoever created it is the owner, and ownership can be transferred to another person in the organisation.
The credential registered in Qlik
The credential belongs to your company
Each workspace connects to Qlik through an OAuth client created in the customer's own Qlik Cloud. Revoking the client in the Management Console ends the access immediately, without depending on a request to our team. At no step of the process does NewHub request or store a user's password.
Identity confirmation remains with Qlik
A user's permissions in the portal are the permissions they already hold in Qlik. There is no second access list to keep in sync, and the portal is not capable of granting more than Qlik grants, even under incorrect configuration.
The Redirect URI is the workspace address
Each workspace has its own address, and that is where Qlik returns the user at the end of authentication. The authentication flow stays within the customer's domain.
The client secret is not displayed again
The value is encrypted on the server at the moment of submission and does not transit the browser again. Replacement is done by generating a new secret in Qlik and registering it in the portal's integration area.
Tenant Admin is recommended, not required
Creating the workspace is possible without the Tenant Admin role, and the creator remains the owner. The difference appears on screens that list instance-wide resources, such as the complete set of apps, spaces and users. Those lists may come back incomplete, because Qlik answers only what the user's permissions reach.
Interruptions during registration
The most frequent cause is a divergence in the Redirect URI. Compare the value registered in the Management Console with the address displayed on the registration screen, character by character, trailing slash included.
A workspace created with an inactive connection is the second case. The portal forwards to a pending screen with a recovery link, and that link operates without an active session. The configuration is resumed from there.