How to build a data portal with your own brand on Qlik

If you have ever wondered how to build a data portal with your own brand on Qlik, what is usually at stake is the experience the end user meets when they open the link they were sent: which colours they see, which logo sits at the top, how the dashboards are organized and how much the whole thing looks like something your company delivered. For managers who distribute dashboards internally or to clients, that perception counts as much as the content of the dashboard. The good news is that there is more than one route there, with very different levels of effort and outcome, from Qlik's native customization layers to ready-made consumption layers such as NewHub. This article walks through each of them so you can choose clearly what makes sense in your context.

What a branded data portal actually needs

A data portal with an identity of its own starts with the visual basics and goes past them. The end user perceives brand when they find the company's colour palette applied consistently across the navigation, typography aligned with the institutional standard, the logo in the right place and, above all, dashboards organized by the business logic they recognize — by area, by process or by client — instead of a list of applications named after the data team's own convention.

Qlik Cloud offers native customization layers that cover a good part of the visual dimension, both at app level and at tenant level, and they are worth knowing well before considering anything bespoke. The architecture decision comes a step later, when the portal has to bring different apps into a single navigation, support distinct arrangements for distinct audiences, and keep that arrangement under the control of whoever publishes, without depending on a development cycle for every change of structure.

Qlik Cloud or Qlik Sense Enterprise: the choice that shapes your architecture

Qlik Cloud removes infrastructure management and delivers automatic updates, which simplifies operations considerably and reduces the data team's effort on environment maintenance. For most portal scenarios, including those involving external audiences, it is the more practical base, because signing in with the corporate account people already use, access control and the embedding APIs are already available with no platform work.

Qlik Sense Enterprise on Windows offers full control over the infrastructure, which makes deep corporate integrations, regulated environments and more complex architectures easier. The trade-off is the responsibility for managing servers, updates and continuous maintenance. For portals that need fine-grained governance control or that operate under strict regulatory requirements, that architecture still makes sense. In branded portal scenarios outside highly regulated environments, Qlik Cloud tends to be the more direct choice.

How to apply native visual customization in Qlik

Qlik offers three layers of visual customization that can be combined. The custom theme controls colours, fonts, sizes and backgrounds across the whole application; it is created as a JSON/CSS file and can be applied per app, aligning the appearance with the company's visual standard. App styling lets you adjust the header logo, the header colour, the visibility of the toolbar and the app icon. The Brands API works at tenant level and replaces default visual elements, such as logos and browser favicons, with corporate images.

Combined, those three layers handle visual customization inside the apps well, and for many teams that is already enough. The decision point appears when the goal moves from the look of the apps to the navigation structure of the portal as a whole, because the native layers act on visual identity rather than on content organization: they don't build a home page split by business area, nor let each user gather dashboards from different apps into a space of their own. The Brands API, moreover, works with one active brand per tenant, which means scenarios with multiple clients in the same environment call for an additional layer above it.

The technical route: mashup, embedding and SSO to publish the portal

A Qlik Sense mashup is an external web application that embeds Qlik objects and visualizations using the platform's APIs. Dev Hub lets you create mashups with a visual editor or with HTML, JavaScript and CSS, connecting to the Qlik app over WebSocket with qlik.openApp. For simpler embedding in external portals, the Single Integration API lets you embed visualizations and sheets via iframe. The result is a web interface with the look and the navigation you built, fed by Qlik's data.

Authentication: connecting external users securely

For secure authentication, Qlik Cloud uses OAuth 2.0/OIDC integrated with the company's identity provider, which enables single sign-on without creating separate logins. The Engine API depends on that prior authentication and comes into play when the embedding needs to interact directly with the analytics engine over WebSocket. On the licensing side, internal users are served with standard Qlik Sense licences; external users, such as clients or partners, generally require a specific contractual arrangement or the use of Qlik Analytics Platform for authorized third-party access.

In practice, the authentication flow for a portal with external users follows these main steps:

• Configure the OIDC identity provider in the Qlik Cloud tenant and register the authentication callback address.
• Create an OAuth client in Qlik Cloud for the external portal and map the user and group attributes.
• Use the authorization flow to obtain the access token and, on top of that authenticated session, consume the embedding APIs in the presentation layer.

Licensing and external access: what to weigh before publishing

Qlik's licensing model distinguishes internal users from external users, and that distinction has a direct impact on the portal's cost and architecture. Before settling on the technical route, it is worth mapping how many external users will have access, how often, and which capabilities they will need — that determines whether Qlik Analytics Platform is required or whether a standard configuration will do.

The real cost of custom development, and when the ready-made route makes more sense

Building a branded portal on Qlik with mashups and APIs requires a team with front-end development knowledge, familiarity with the platform's APIs and the capacity to maintain the integration across product updates. Beyond the initial development there is the ongoing cost of maintenance: every update may require adjustments to the mashup, and any new app added to the portal has to be integrated by hand. That second block is the one that usually escapes planning, because it has no end date and grows along with the number of published apps.

For teams with few technical resources, or with demands that evolve quickly, that cost accumulates without ever appearing in the initial budget. A simple mashup can start in the tens of thousands; a complete corporate portal, with SSO, access rules, responsiveness and support, easily runs into the hundreds of thousands. For organizations with dedicated teams and very specific requirements, the technical route makes sense and delivers exactly what was specified. What matters is entering it clear about what is being bought.

How to build a branded data portal on Qlik using NewHub

NewHub was built to shorten that cycle. It is a consumption layer built on Qlik Cloud, in which logo, colours and typography are configured directly, with no custom code, and the navigation is arranged by business area, by process or by client, following the logic your audience recognizes. The integration with Qlik is done over OAuth, with no data migration, and the permissions already defined in the environment, Section Access included, keep applying in the NewHub layer, which preserves the existing governance with no additional configuration work.

Each user can organize their own view by gathering dashboards from different Qlik apps into a single space, without depending on the IT team for every adjustment. Single sign-on over OAuth/OIDC is already integrated with the company's identity provider, with per-tenant isolation and granular access control. Conversational AI is available across NewHub's plans, letting anyone query the data in plain language and get answers as text or as a chart, without opening a ticket to the BI team. And the adoption module records who accesses what and how often, which gives whoever answers for the BI investment an objective picture of engagement to support the renewal and licence-expansion conversation.

For ISVs, consultancies and data teams that need to distribute dashboards under the client's visual identity, NewHub offers a direct route between Qlik Cloud and a portal ready for the end user, with customization, governance and data assistance brought together in a single platform.

Choosing the right route to a branded data portal on Qlik

Building a data portal with your company's identity on Qlik is possible along different routes, and the right choice depends on how much technical effort you have available and on the level of customization you need to deliver. For customization inside the app environment, the native tools, such as custom themes and the Brands API, do the job well. For an external portal with bespoke embedding, the mashup and extension route is robust, and it demands continuous technical investment.

If the goal is a portal with a complete visual identity, navigation organized for the business user and AI assistance included, without building from scratch, NewHub is the most direct route. You start from what you already have in Qlik Cloud and arrive at a portal ready for the end user far more quickly. See how NewHub works in practice.