First steps
Access address, authentication, information security, and data integrity.
The portal is reached at a single address, in the form yourcompany.newhub.com.
Recording it in the browser's bookmarks is recommended.
Authentication
When accessing the workspace URL, the user is directed to the Qlik Cloud authentication screen. Authorisation is requested on first access only. The return to the portal is already authenticated.
There is no NewHub password. Identity is confirmed by your company's Qlik Cloud, under the same credentials and the same rules your data team already maintains.
The sign-in protocol
Sign-in uses OAuth 2.0 in Web mode, with a confidential client and PKCE. The client is created in the company's own Qlik Cloud, and its secret stays on the portal's server only.
The exchange of the authorisation code for tokens happens server to server. The access token and the refresh token never reach the browser.
Revoking the client in the Qlik Management Console ends access for every user of that workspace immediately.
Information security
Tokens and secrets encrypted at rest. The Qlik tokens and the workspace's client secret are encrypted before being written.
Analytical data is not copied. The portal queries Qlik at the moment of use and keeps no replica. What it stores is configuration: collections, pages, favorites, the individual dashboard layout, and usage records.
Reliability and integrity
Responsibility of calculations. The indicator displayed is calculated by Qlik, using the measures your team published. The portal neither recalculates nor stores a previous result, so the value on screen and the value in the source app do not diverge.
Verifiable calculation. The agent's answer reports which app, which measures and which filters were used.
Permissions are always Qlik's. The portal grants no access to an app, a space or data. A permission change in Qlik applies on the next query, and losing access interrupts the loading of any card or answer depending on that app.
Hosted in a Brazilian region. The application and the configuration database run in São Paulo. Analytical data stays in your company's Qlik Cloud.
Content visibility
An app is displayed when the user holds permission for it in Qlik. The portal does not widen access under any circumstances. It organises the presentation of what the user could already open.
A difference in visibility between two users indicates a difference in Qlik permissions. The adjustment is made by the workspace administrator.
Session expiry
After a period of inactivity the Qlik session expires and the portal displays a notice at the top of the screen. Selecting it restores the connection and preserves the working context, including applied filters and the tab in use.
Frequent recurrence of the notice should be reported through the support menu. The ticket automatically records the screen in use at the time it was raised, which removes the first round of questions.