Frequently asked questions
What NewHub is, who it serves, what it requires from Qlik, and what it does not do.
The questions below are the ones that come up before an evaluation, both from the people who will use the portal and from the people who approve the purchase.
What is NewHub?
NewHub is an analytics portal for companies running Qlik Cloud. It gathers the approved apps, pages and links at a single address, under the company's branding, and adds search, favorites, a per-person dashboard, and questions in plain language. The apps stay in Qlik: the portal is the consumption layer, not a second BI tool.
Who is it for?
For the people who consume the number rather than build the analysis: leadership, management, sales, operations, finance. They need two or three indicators a week, not a catalogue of objects, versions and spaces.
For the data team, the portal is where the curation already done in Qlik reaches the end user, with a record of who opened what and which questions were asked.
What is conversational analytics, and how does it work here?
Conversational analytics means getting a number by asking in plain language, with no dashboard to open and no expression to write. In NewHub that is Ask Agent: the question is written in Portuguese, English or Spanish, the agent queries the Qlik app the administrator prepared, and returns the text, a suitable chart, and the calculation used, naming the app, the measures and the filters.
The answer respects the permissions of whoever asked. Two people with different access receive different numbers for the same question.
Does NewHub replace Qlik?
No. Qlik remains where data is modelled, measures are defined and apps are published. The portal queries Qlik at the moment of use and recalculates nothing. When a number is wrong, the correction happens in the source app.
Do we have to migrate apps, remodel data, or change licences?
No. The apps stay where they are, the Qlik licence remains your company's, and the data team keeps working in the usual tools. The portal does not copy, move or store analytical data.
How long does it take to go live?
Registration has four steps, and the only one that takes work is creating an OAuth client in the Qlik Cloud Management Console, which takes a few minutes for whoever administers the tenant. After that the portal already opens with the apps the user could see.
The remaining time is curation: deciding what appears in the menu, building collections, and preparing the apps the agent may query.
How do permissions work?
They are Qlik's, with no second list. An app appears for whoever already had permission on it, and the portal cannot grant more than Qlik grants, even when misconfigured. A permission change in Qlik applies on the next query.
Do we have to install anything?
No. The portal is reached through the browser and requires no agent, plugin or software on your company's infrastructure. There is no VPN, tunnel, internal directory integration or connection to databases on your network: communication goes to the public address of your Qlik Cloud tenant, over HTTPS.
On the Qlik side, the only configuration is an OAuth client created in the Management Console, with the return URL, the allowed origin and the permissions the portal uses. The registration screen hands you those values ready to copy.
How does authentication work?
Through OAuth 2.0 in Web mode, with a confidential client registered in your company's Qlik Cloud. On sign-in the browser is taken to Qlik Cloud, which forwards to the corporate identity provider. The portal receives the person's identity back, never their password.
The renewal token stays on the server, encrypted. What reaches the browser is only a short-lived token, held in memory, which the official Qlik component uses to render dashboards. That token grants nothing beyond what the person can already do in Qlik.
Will we have a new username and password, on top of Qlik?
No. There is no NewHub password, no parallel user base and no invitation that creates access to data. Whoever signs in to the portal is whoever already signs in to Qlik Cloud.
The SSO and MFA configured in your company's identity provider keep applying, with no additional integration. Deprovisioning is automatic: someone disabled in the directory loses access to Qlik and, with it, to the portal.
Where does the data live?
Analytical data stays in your company's Qlik Cloud. The portal queries at the moment of use and does not copy, move or store values.
The portal's database holds configuration and metadata: user identification (Qlik identifier, name, email, role in the portal), the curation of the menu, dashboards people build, favorites, support tickets and operation records. The database is hosted in São Paulo.
How is data security ensured?
The portal never widens anyone's access. What each person sees is what Qlik Cloud already allows them, and that holds even if the portal is misconfigured.
What we do store is kept separate per customer, and that separation is enforced by the database itself, not by application code. Integration credentials and tokens are encrypted, traffic is always HTTPS, and sessions expire on inactivity and at a maximum age.
For a formal assessment we provide a technical dossier with the architecture, the controls in force and the known gaps, point by point.
Is there an audit trail of access and changes?
Yes, per workspace, and the trail is immutable: the database refuses to alter or delete a record once written. Recorded, with author, date, IP address and user agent: each person's sign-in and sign-out, changes to user role and status, decisions on access requests, ownership transfer, and changes to the integration credential and to workspace settings.
Reading and exporting the trail are served on request. Separately, administrators follow the last seven days of usage in the interface: who opened which dashboard and what was asked of the assistant.
Does it work with Qlik Sense on-premise?
No. The product connects to Qlik Cloud, which is where the OAuth client used for authentication exists. A Qlik Sense environment installed on the customer's own infrastructure is not served.
What about Power BI, Tableau or other tools?
A link to an external report registered inside a Qlik space appears in the portal's search and opens in a new tab. There is no native Power BI or Tableau embedding: the content rendered inside the portal is Qlik's.
Which languages does the portal support?
Portuguese, English and Spanish, including the administration area and this documentation. The default language is set per workspace, and each person can use a different one.
What does it cost?
The trial runs for 14 days and requires no credit card; the user and question limits for the period are shown on the registration screen. The Qlik licence remains your company's, so the portal adds no BI licence cost. For prices and terms, write to support@newhub.com.
How do we get help?
Through the support menu, inside the portal itself. The ticket automatically records the screen in use when it was raised, which removes the first round of questions.