What's new
What changed in the portal, version by version. Releases carrying only internal maintenance are not listed.
Usage analytics on a single 7-day window.
Improvements
- Usage analytics — who accesses the portal and what people ask Ask — now use a single 7-day window, the same across every screen. Older usage data is no longer kept, and the 30- and 90-day periods that existed in Ask analytics are no longer available.
Text that stayed in Portuguese for people using the portal in English or Spanish.
Fixes
- Some text showed up in Portuguese even with the portal in English or Spanish: image upload (drag hint, accepted formats, error), pagination in the engagement tables, the collection form, the featured-app picker in groups, and the labels in the confirmation summary when saving appearance. They now follow the chosen language. Error messages coming from the server do not follow the portal language yet.
The administration panel says when the Qlik connection allows less than it can show.
Improvements
- Administrators now see a notice in the administration panel when the Qlik Cloud connection does not yet allow listing the tenant's full catalog — common for workspaces created before this capability existed. The notice links straight to the Integration screen, which shows what is missing to allow, and can be dismissed; each person dismisses their own.
Fixes
- The Settings screen showed an old identifier of the Qlik connection, from before the authentication mode changed, which for older workspaces no longer matches what exists in Qlik Cloud. The field is gone; the Integration screen is the place that shows the credential in use, with its real state.
The setup screens showed fewer permissions than the portal uses.
Fixes
- The workspace setup and recovery screens showed two permissions to register in Qlik Cloud, while the portal had moved to four. Copying from there produced an incomplete credential, and the effect only surfaced much later: the administration screens that list the apps and spaces of the whole instance came up empty, with no explanation. Both screens now show all four, and the setup guide explains what each one unlocks and warns that the change only takes effect on the next sign-in.
When sign-in fails, the screen gives the probable reason.
Improvements
- Any failed sign-in used to show the same generic sentence, even when trying again would not help. The screen now gives the probable reason and what to do, with a reference code to pass on to whoever administers the portal. Administrators find the same list, in more detail, on the Integration screen. The list keeps recent failures only and starts over on every service restart.
The Integration screen shows which permissions Qlik granted.
New
- Administration → Integration has a panel showing, one by one, the permissions Qlik Cloud granted the portal on the last sign-in: what already works, what is missing and the practical effect of each gap. When one is missing, a warning appears in the menu next to the affected screens, with the way to fix it. Some Qlik environments do not report this list; the panel then says it does not know, rather than flagging a problem that may not exist.
Signing out now brings you back to the portal's own screen.
Improvements
- Signing out used to end on a Qlik Cloud page that was sometimes just the word “OK” on a blank background, which looked like an error. The sign-out now happens in the background and the last screen is the portal's own, with the button to sign back in. In some browsers your Qlik session may stay open; the screen therefore offers a link to end it too, which matters on a shared computer.
Administrators can see the full Qlik catalog in the admin screens.
New
- Workspace administrators now see every managed space and app in the Qlik environment from the admin screens, even without being a member of each space. It was the missing piece to configure folders, highlights and spaces without requesting access one by one. To enable it, allow the space and app read permissions on the Qlik Cloud connection and sign in again; the Integration screen names exactly which ones. Seeing an app in the catalog is not the same as being able to open it, and outside administration the portal stays personal: menu, search and app pickers keep showing each person only what they can open.
A dashboard idle for 15 minutes pauses, and comes back in one click.
Improvements
- After 15 minutes without interaction with the portal, Qlik dashboards pause: the connection is closed, which stops consuming your environment's license and avoids the expired-session screen Qlik used to show on its own. One click on Resume brings everything back in place. Selections made before the pause start over, and while you are clicking inside a dashboard it does not pause.
Empty spaces and apps screens now explain why.
Improvements
- When no space or app shows up, the screens now explain the most common cause: the list follows your user's access in Qlik Cloud. Being a Tenant Admin grants no content access; seeing a space requires membership, and seeing every managed space requires the Analytics Admin role. The notice appears in the side menu, the Spaces screen, the app picker and the Ask preparation.
The spaces and apps you see in admin now always show in the portal too.
Fixes
- In some environments, spaces and apps showed on the admin screens but not in the portal menu, for the same user. Both screens now query Qlik through the same path, so they show the same content. As a bonus, workspaces with more than 50 managed spaces now list all of them, not just the first 50.
You can switch accounts even while access is awaiting approval.
Fixes
- Signing in with the wrong account on a workspace that requires approval used to trap you in it: the waiting page had no action and every attempt came back as the same account. The error and waiting pages now have "Sign in with another account", which ends the Qlik session in that browser so you can come back and sign in with the right one.
Changing your Qlik identity provider no longer breaks the workspace.
New
- When your Qlik tenant switches to another identity provider (Microsoft Entra, for example), each person comes back with a new identity. The portal now recognizes on its own who has the same email and reconnects favorites, dashboards, role and history to the existing account. And when the email changed too, admins gained a third action on access requests: link to an existing member, instead of creating a user from scratch.
Improvements
- Whoever creates a workspace now needs an email on their Qlik account: it is where the recovery link goes if the connection ever breaks. The creation wizard explains how to set it up. The users screen also warns when no admin has an email on file, a state where access requests notify nobody.
Fixes
- Automatic session renewal no longer switches users silently: if the Qlik session in the browser belongs to someone else, the portal asks for an explicit sign-in instead of completing as the other user.
Signing out now really signs you out, and you can sign in as another user.
Fixes
- Signing out of the portal now also ends your Qlik session, which chains through to your identity provider. That makes it possible to sign in as someone else in the same browser, which previously did not work: clicking sign in brought back the same user. Note that signing out of the portal now ends the Qlik session in that browser, including other hub tabs.
The recovery link now goes to whoever administers the workspace today.
Improvements
- When Qlik does not provide the email of someone requesting access, the notification to the admin now says so and shows that person's Qlik identifier instead of an empty field. And if the email starts coming through later, the pending request corrects itself on the next sign-in.
Fixes
- The emergency link that unlocks a workspace was going to the address of whoever created it, even after ownership had been transferred. It now goes to the current owner and the active admins, and no longer to people who merely signed in once. Nothing to do on your side: it applies from the next request on.
- People who joined the workspace after it was created are now found by "forgot my workspace". The email index previously held only the person who created it.
Compatible with stricter identity policies, and sign-in failures visible to admins.
New
- The portal now adapts on its own to what your Qlik environment grants. If Qlik allows renewable sessions, they last through the workday, as always. If your identity provider blocks that permission, sign-in still works: each session lasts about an hour and renews through a quick redirect that completes without a new password prompt while the Qlik session is alive. Change the configuration in Qlik and the next sign-in follows the new state, with nothing to touch in the portal. The limit: in that mode the page reloads on each renewal.
Improvements
- When a sign-in fails because of a missing permission in the Qlik configuration, the error page now says exactly which one, instead of a generic error. And every failure shows a reference code: sending it to support points straight at the exact cause, with no back and forth.
Finding a Qlik app is now typing its name.
New
- When adding a Qlik app, you now search by name or filter by space instead of scrolling the whole list. It works in Folders & Content, in a group's featured items, in My Analyses and on the Ask preparation screen, with a bigger window and more apps loading as you scroll. The space filter has a search of its own. Search matches the app name, not the description, and only apps in managed spaces appear, which are the ones the portal can open.
- The Spaces screen gained search by name and filters with counts: All, Customized and Default. With many spaces around, you can see at a glance what has not been configured yet.
Improvements
- Screens that list apps open faster: a per-app computation, redone on every listing and shown nowhere, was removed.
Fixes
- No app is left out of the list any more. In large environments the portal stopped loading the Qlik catalog past a certain point, with no warning, so an app that existed looked like it did not.
- Drag-to-reorder in Folders & Content works again, for folders and for the items inside them, and the new order shows up immediately, with no flashing.
- On the Users screen, the total shows again from the second page on: clicking Next used to zero the count.
- Opening an app from a saved link, a browser bookmark or a link someone sent you now leaves the sidebar in the right place: the app's space or collection expands, the app shows highlighted, and the menu scrolls to it, even when it sits far down the list.
The Users screen opens and searches in workspaces with thousands of people.
Improvements
- Searching by name, email or identifier on the Users screen is now answered by Qlik Cloud itself, so it finds the person wherever they sit in the directory. In exchange, the numbered page buttons gave way to Previous and Next: Qlik serves the listing in sequence and cannot jump straight to a specific page, and forcing that was exactly what froze the screen. To find someone, search beats any page number. In the "no access" filter, the count at the top is an estimate and a page may come with fewer rows than usual, or empty with Next still available — that is the portal comparing Qlik's directory against your members in chunks, to keep it light; keep clicking Next to move on.
Fixes
- The Users screen used to freeze in large workspaces: before showing the first ten rows, the portal downloaded the complete list of users from Qlik Cloud, and did it again on every filter and every search. With thousands of people in the directory the screen never loaded. The portal now asks for one page at a time and the screen opens normally, whatever the directory's size.
Generate each part of an app's AI context individually.
New
- Ask now has a switch under Settings → Features: turned off, the assistant goes off the air for the whole workspace — the menu entry, the Ask page, the assistant inside apps, the floating window, the AI section of the admin panel and the Ask metrics on the Engagement screen. Nobody can ask a question and nothing is charged while it is off. In the admin panel the AI entry does not vanish: it stays dimmed and explains on hover that Ask is switched off, with a button that goes straight to the switch. Conversations and all app preparation are kept and come back exactly as they were when you turn it on again.
- When preparing an app for Ask, each context section (context, rules, assumptions, restrictions, vocabulary and examples) now has its own AI-generate button. The draft comes out tailored to that section's purpose, consistent with what's already written in the others, and in the language you use the portal in — review before saving, as always.
- Ask's validated queries can now be born from the charts the BI team already built: a sidebar lists the app's sheet objects and shows the real chart live and unfiltered, with the query it runs, so you can check it before importing as an editable copy or linked to the object. Linked, the query always uses the chart's current definition — changes made in Qlik apply to Ask automatically. The imported query copies the chart settings that change the number (zero-row suppression, calculation condition, alternate state, the Top N "Others" slice); what it cannot repeat — accumulation, moving average and drill-down groups — is flagged before you import. The editor shows the full definition sent to Qlik.
- An Ask answer's "How it was calculated" now names the query that ran and, when it is a query validated by the BI team, shows the certified badge with who validated it and when. The result itself stays clean, with no badge on the outside: the number's origin lives in one place, one click away.
Improvements
- The charts in Ask's answers were redesigned: a new palette, tested to stay readable for colorblind viewers and with its own set for dark mode; a single-measure chart now uses a single color; bars with few categories show the value at the tip; and grid, axes and tooltips became quieter. Stat cards and tables were refined too.
- Ask's admin got clearer: an app's states and privacy mode now explain what they do, the test chat is visible, and each app can have its own display options. The usage and feedback screens now filter several apps and users at once, and question volume became a line chart by day, month or year.
- Numbers in Ask's charts now come out formatted: the chart respects the measure's format in Qlik (currency, percentage, decimal places, unit) and your language's thousands separator, instead of showing the raw number on the axis and tooltip. You can also ask for a different presentation in the conversation — "in millions", "no cents", "as a percentage" — and the chart is redrawn.
- The public documentation is now more comfortable to read, with text at the browser's standard size.
Fixes
- Ask's floating window is now stable: opening it no longer breaks the screen, it no longer shows a menu button that did nothing, and inside a dashboard the dashboard gets the full width back while the chat floats on top.
- In privacy-enabled apps, Ask no longer claims to have drawn a chart that never appeared on screen, nor describes numbers in that case. When a result cannot be displayed, it says so instead of making it up.
Ask in a floating window that follows you around the portal.
New
- On the Ask page, a new button pops the chat out into a floating window that stays open while you browse dashboards, collections and pages — the conversation isn't lost when switching screens. Available in browsers with Document Picture-in-Picture support (desktop Chrome and Edge).
Improvements
- Portal notifications (tickets and Ask alerts) now arrive in each person's language, following their profile — they were previously always in Portuguese.
Fixes
- The notifications panel in the admin area now uses the admin's neutral colors and opens in the right direction, instead of wearing the portal menu's custom colors.
Each person sees only the apps they have access to.
Fixes
- App lists are now computed individually for each user, and Ask only offers apps the user can actually access in Qlik, even when the app is AI-enabled for the workspace.
The data Ask queries is never stored readable on our servers.
Improvements
- Ask's answers are now stored encrypted, and the technical records of each query keep only metadata (column names and row counts), never your data's values. Chat, history and the administrator screens keep working exactly as before.
Security tightening and fixes to the Ask screen.
Improvements
- Disabling a user in the admin panel now ends their access immediately, including to Qlik dashboards and the Ask chat, without waiting for the session to expire.
Fixes
- The Ask negative-feedback alert now reaches the administrator instantly, without reloading the page, and clicking it opens the Feedback tab directly.
- Dates and numbers on the Ask screens now follow the workspace language, instead of always appearing in the Brazilian format.
- Fixes to the admin Ask screens: per-app usage shows an error when loading fails instead of displaying zeros; the app and user filters no longer stay stuck on an invisible value when the period changes; and the floating-window chat no longer freezes the page when opening context editing.
Rate Ask's answers, and the portal turns real usage into improvement suggestions.
New
- The Ask chat, opened inside an app, can now become a floating always-visible window, freeing the whole screen for the dashboard. It is the same conversation, no restart. Available in browsers that support content picture-in-picture, such as Chrome and Edge; elsewhere the button does not appear.
- Every Ask answer can now be rated with a thumbs up or down, and a negative rating accepts a comment on what went wrong. Ratings show up for administrators in the usage area and on each app's preparation screen, with the calculation that produced the rated answer and a shortcut to open the app and check. Negative ratings raise a notice, at most one per app per day. Rating takes one click and improves everyone's next answers.
- For administrators: an app's readiness assessment now looks at the last 30 days of real usage and returns suggestions ready for review, such as validated queries prefilled with what users actually asked, filter values that don't match the data, and context drafts based on poorly rated answers. Nothing applies on its own: every suggestion goes through the usual review.
Improvements
- For administrators: preparing an app for Ask now happens on a screen dedicated to it, opened by clicking the list and with a back button. Inside there are two tabs, one for context and queries, another for the app's usage. The Ask area also gained a Feedback tab, with the full ratings table filterable by app, user and period, and usage now shows the name of whoever asked.
Fixes
- Filters applied on the dashboard no longer interfere with Ask's answers. Before, a question like "how many patients do we have?" could answer the number of the filtered slice on the dashboard, without saying so. Ask now always answers over the app's full data, respecting permissions, and only considers the dashboard filters when you explicitly ask, showing them in the calculation.
A complex question no longer ends with no answer, and Ask follows each app's rules in general questions too.
Improvements
- Ask is better at recognising when a validated query answers the question: beyond the name and description, it now sees what the query groups by, what it measures, and the example question registered by the administrator.
Fixes
- When a question required many steps, Ask could exhaust the step limit and finish showing the list of steps and no text. It is now required to close with what it gathered, even when the conclusion is that it could not answer, and why.
- The constraints and vocabulary written for an app only applied when the question was asked from inside it. They now apply on the Ask page as well, where the question is asked without choosing an app.
Corrections regarding AI quota usage.
Fixes
- When an answer did not arrive due to a failure of the AI provider or Qlik, the question was still deducted from the workspace quota. Now only answered questions count. A question interrupted by the person who asked it still counts.
Documentation with language-specific slugs, and general navigation improvements on the documentation page for phones.
Improvements
- Every documentation page now has an address in the language it is written in. Old addresses keep working: a saved link now forwards to the new address automatically.
Fixes
- On phones, the documentation would not scroll past the first screen and the menu took up the top of every page. The menu now opens from an icon in the header, in a side panel that closes when a page is chosen, and the text scrolls to the end as expected.
Documentation centre, in Portuguese, English and Spanish.
New
- The product documentation is available at docs.newhub.com, in all three portal languages. It covers everyday use, from first sign-in to asking questions in plain language, and includes a walkthrough of creating a workspace.
Search now also finds links registered in your Qlik spaces.
New
- When someone registers a link to an external resource inside a Qlik space, that link now appears in the portal's search and opens in a new tab. It suits a report maintained in another tool, a legacy system, or an internal company page.
Improvements
- Search now lists only content published in governed spaces.
Continuity in conversations with the agent, and more context for administrators preparing answers.
New
- When preparing an app for the agent, administrators can now register example questions and describe the meaning of each measure and dimension. The agent uses that vocabulary in its answers, bringing the result closer to the language the business already uses.
Improvements
- Follow-up questions now reuse the query and the chart of the previous answer.
- The agent's answers now carry only the content intended for the person who asked, without notes from its own processing.
The chart for each answer is now chosen automatically.
Improvements
- The visual form of an answer is decided from the data returned. A comparison across categories arrives as bars, a trend over time as a line, and a composition as a pie, without anyone having to ask. Before this, a good share of answers came as text only.
Fixes
- Workspaces configured in privacy mode were receiving answers without the chart. The chart is now presented in that mode as well.
Workspace creation no longer requires the Tenant Admin role in Qlik.
New
- Registration now accepts people without the Tenant Admin role in Qlik Cloud, and that person remains the owner of the workspace created.
Fixes
- An item inside a collection would not open when selected. Opening was corrected.
- A new workspace now starts with the product's default theme colour.
Workspace recovery, dashboard cards opening on the right sheet, and appearance settings that were not being saved.
New
- A workspace whose Qlik connection is inactive now presents a recovery screen, with an access link that works without a session. Before this, the only way out was to contact support.
- A card on the individual dashboard pointed at a specific sheet of an app now opens directly on it. The card previously led to the app's start and navigating to the sheet was left to whoever clicked.
Improvements
- Registration now validates the credential in Qlik before forwarding the browser to the authentication screen.
Fixes
- Some appearance fields were not saved correctly. Now all fields are persisted and reflected in the portal.
A session resilient to momentary Qlik instability, and the administration area in three languages.
Improvements
- A momentary failure renewing the Qlik session no longer signs the user out. Renewal now distinguishes temporary unavailability from a genuinely invalid credential, and only the second case ends the session. In practice, this ends sign-outs during work caused by network fluctuation.
- The engagement and appearance screens in the administration area became available in English and Spanish, completing the product's language coverage for whoever administers the workspace.