White-label Qlik Sense dashboards: how to deliver them to clients

The consultancy delivered. The dashboards are live on Qlik Cloud, the loads run on schedule, and the people who asked for those numbers can reach them. Technically, everything stands. But when the client opens the browser, what they find is the environment where their analysts work: a Hub organised by spaces and apps, following the logic of people who build analysis. That is exactly what that environment should be for the people who live in it. What is missing is something else: nothing there speaks of the client's business, and nothing recalls the project they paid for. The delivery is real; the perception is of somebody else's tool.

This is a practical guide for consultancies, ISVs and integrators who deliver analytics on Qlik Cloud and want the result to look like the product they sold. It covers what changes when the environment carries the client's brand, how to choose where to build it, what to ask the client for before you start, and what to check before you present. If your question is the more technical one, about which Qlik layers let you customise what, the guide on how to build a data portal with your own brand on Qlik is the place to go; this article is about the delivery.

Why branding changes how a technical delivery is read

There is no need to invent a statistic to support this. People who use a system every day can tell the difference between what belongs to their work and what is a tool they are passing through. An environment carrying the company's logo, its colours and a navigation organised around the language of the business reads as part of the operation. A neutral environment reads as something somebody installed, and that might be gone tomorrow.

It is worth being honest about the size of the effect: branding does not produce adoption on its own. A beautiful portal full of dashboards nobody asked for stays empty. What visual identity does is remove one specific friction, the user not recognising the environment as theirs, and that matters most in the population that is hardest to engage: the people who are not analysts and do not open Qlik out of habit. For the consultancy, the side effect is commercial. A delivery that looks like a product sustains a support contract, a renewal, and pricing based on perceived value rather than on development hours.

When branding should already be in the proposal

Not every project needs the client's brand on day one. Some need it from the proposal onwards, and recognising that early avoids the awkward conversation of selling later what should have been in scope. The clearest signals are business users, not only the technical team, among the recipients of the dashboards; the delivery being part of a managed analytics offer; the client wanting to distribute information to branches, partners or their own customers; and a long contract horizon, with support and renewal at stake.

Where to build it: the questions that rule options out

Building an analytics portal from scratch means taking on the security architecture, the update cycle, the maintenance and a few weeks before the first useful screen. There are cases where that is justified, usually when the portal is the company's product rather than the wrapper around a delivery. For most consultancies the arithmetic does not work, and the shortest path is a layer that already rests on the governance configured in Qlik Cloud.

Before choosing, four questions rule out most of the alternatives. How much of the brand the platform actually applies, logo, colours and typography included. What address the portal runs on. Whether sign-in integrates with the identity provider the client already has, or creates one more password for somebody to administer. And whether the access rules configured in Qlik keep applying, or everything has to be rebuilt on the other side.

The question about the address deserves precision, because it is where answers diverge most and where proposal promises tend to break during rollout. Some platforms host the portal on a generic vendor address, some give a dedicated subdomain per client, and some accept the client's own domain. With NewHub, the standard subscription includes a dedicated subdomain, in the form workspacename.newhub.com, with managed TLS. The client's own domain is possible too, outside the standard plan, and that is worth settling with the team before the proposal goes out. Either way, fix the address before signing rather than after.

Why a layer built on Qlik Cloud changes the arithmetic

A layer built on Qlik Cloud, such as NewHub, removes any need to migrate or copy data: the tenant is connected through an OAuth client and the data stays where it is. Sign-in uses OAuth 2.0 and OIDC on top of the identity provider the client already runs, whether that is Entra ID, Okta or another, so nobody has to administer a second set of passwords. And the governance already configured in Qlik keeps governing what each person sees.

That last point saves the most rollout time, and it is also the easiest one to promise wrongly. The inheritance covers what Qlik controls in access to data, including the row-level security configured in the apps. How the portal itself is organised, which dashboards appear for whom and in which collection, is portal configuration, done by whoever publishes. Document that boundary for the client at handover, because it is where permission misunderstandings are born.

The brand kit to ask for before you start

Before you open the configuration, ask the client for the logo in its main and reversed versions in vector format, the palette with the exact HEX codes, the official typography with its usage hierarchy, and the favicon, usually the logo mark reduced. Asking early avoids the most common last-minute rework: finding out the evening before the presentation that the only logo available is a low-resolution PNG, or that no version exists for dark backgrounds.

Validate as a user, not as the person who configured it

Once the brand is applied, enter the environment the way a business user would, with a test profile that has no administrator privileges. Check the contrast between text and background across the different states of the interface, the legibility of the logo at the size it actually appears in the navigation, and how the favicon behaves in the browser tab. Confirm too that the portal's accent colour agrees with the colours used inside the dashboards: a mismatch between the menu and the chart draws attention for the wrong reason, and it is exactly the kind of detail a client notices in the first meeting.

Technical checklist before handing over

• Portal reachable at the agreed address, with a valid certificate and no browser security warning
• Logo, colours and typography applied consistently across navigation, loading screens and error messages
• Sign-in tested end to end with the client's identity provider, including a brand-new user's first access
• Every profile tested one by one, from administrator to view-only, confirming what each one does and does not see
• Row-level security checked with two users from different areas opening the same dashboard
• Activity trail switched on, with the test sessions visible in it
• Favicon loading in more than one browser

Commercial checklist so the delivery does not turn into friction

• Scope of the environment delivered, with the list of dashboards and sources included
• Maintenance responsibility defined item by item, separating what belongs to the portal, to Qlik and to the client
• Service level agreement with availability, response time by severity, maintenance windows and explicit exceptions
• Acceptance criteria recorded and confirmed by the client
• Next steps documented for new dashboards or new areas

What you gain by delivering the environment in the client's brand

Applying the client's brand is not cosmetic finishing. It is what makes a technical delivery be read as a product, and products get renewed, extended and recommended. For anyone working on Qlik Cloud, the shortest path is a consumption layer that rests on the governance already configured and lets you apply the client's identity without opening a development front.

NewHub was built for this scenario: the client's logo, colours and typography, a dedicated subdomain with managed TLS or their own domain when the project calls for it, sign-in through the identity provider they already use, tenant isolation enforced in the database and a complete activity trail, on the same Qlik Cloud and with no data migration.

The checklist in this article holds for whichever platform you choose. What it protects is the part of the delivery that never appears on the schedule and is the first thing the client notices: the sense that this was made for them.