How To: Qlik Sense Branding 2 – White Label the Hub

Qlik sense Branding 2 - The Hub - Featured Image

What Are We Trying To Do

In our first installment on Simple Qlik Sense Branding, we spoke specifically about adding logos and sheet images at the application level.

There are also opportunities to white label the Qlik Sense hub. Taking the branding to this level allows to basically replace all the Qlik Sense logos and icons with a set of our choosing. After completing this exercise, the hub will appear to be from your company, not from Qlik.

Danger – Proceed at Your Own Risk

Danger IconThis is not a Qlik supported feature. If you go to Qlik Support with a problem arising from white labeling your hub, they will not be able to help you.

In addition, LivingQlik does not endorse this either. We are providing the steps that worked for us, but you should not take that to mean it will work for you or as an endorsement from LivingQlik to go ahead and implement this on your server.

Temporary Solution – Ultimately when you decide to upgrade the Qlik Sense server to the next service release, I am pretty sure these files get rewritten. This means that to keep this going, you might have to replace these files after each upgrade. I would be interested in a permanent fix for this. I thought about writing a new location within the html but then I realized that likely gets rewritten also.

OK, now that the disclaimers are out of the way…

How to White Label the Qlik Sense Hub

In a nutshell, the favicon and logos that you see in the hub are .ico and .png files located in Program Files. If you replace these files, you will see your replacements in the hub. Here are the steps to follow:

1. Logo File Creation

First, use a graphics program to create the logos you desire. These files will need to be named exactly as below, maintain the correct file type and have the correct pixel width and height. These are the ones I prepped for our example:

LivingQlik favicon

favicon.ico

Size: 64×64 pixels

Note that it is super-easy to convert a .png to an .ico file at this site: http://convertico.com/

LivingQlik favicon

logo-60×60.png

Size: 60×60 pixels

logo-76x76.png

logo-76×76.png

Size: 76×76 pixels

Living Qlik - logo-120x120.png

logo-120×120.png

Size: 120×120 pixels

LivingQlik - logo-152x152.png

logo-152×152.png

Size: 152×152 pixels

LivingQlik - qlik-sense-server.png

qlik-sense-server.png

Size: 548×79 pixels

LivingQlik - sense-server.png

sense-server.png

Size: 346×66 pixels

2. Stop the Qlik Sense Server Services

Next, stop all Qlik Sense services. I am not an expert on which service(s) should be stopped or how this will effect a multi-node environment. But I think as a best practice, we would stop the services before changing any of these files.

3. Make a Backup

Please be sure to copy the original files off to a folder somewhere in case something goes wrong. Although I would say this relatively harmless operation, you never know what could go wrong.

4. Replace the favicon

The favicon is the little icon you see on the tab of your browser. Replace the favicon.ico located here (as of 3.1.1): C:\Program Files\Qlik\Sense\Client\

5. Replace the logo files

The logo files have mostly to with the Qlik Sense branding graphics you see in the upper left of the hub, although I am not quite sure where all of them appear. It seems that there are different sizes likely meant to be replaced when the real-estate changes (responsive design). I went ahead and replaced anything that looked like it was server related. I left the desktop versions alone.

As of version 3.1.1, all these files are located here:

C:\Program Files\Qlik\Sense\Client\img\core\logo

6. The hub header stripe

I admittedly did not get this step to work. If you change a hex color in the hub.css file, you should be able to get the color of this stripe to change. I found the class in the css file but was unable to save the file due to security issues on my server. Being that it was already green, I didn’t bother to work through the issue. The hub.css file (as of 3.1.1) is located here:

C:\Program Files\Qlik\Sense\Client\hub

Change the color located in class qui-toolbar-footer

hub_css_color-change

7. Restart the services, check your results

These are the results I was able to achieve. Please also note that users might need to clear their browser caches to see the new logos.

Qlik Sense White Label Results

Final Thoughts

The basis for this post was provided in this Community Document although the path locations have changed since 3.0.

Are there other interesting opportunities here? Or perhaps a more robust way to do this. I am excited to hear your comments.

Thank you for visiting LivingQlik.

4 comments… add one
  • Reply Julian Villafuerte November 15, 2016, 5:47 pm

    Great tip Aaron! I still feel a little restricted when using Sense (I guess I got used to QlikView’s features and great flexibility in the design end) but you reminded us there’s always a way to customize your apps 😉

  • Reply Aaron Couron November 15, 2016, 7:40 pm

    Thanks Julian. I think as time goes on, we will be able to do everything we do today in QlikView but then so much more because of the html5 platform and extendability. I am warming up to Sense 🙂

  • Reply GrangerG March 1, 2017, 6:05 pm

    FYI, you don’t have to bounce the Windows Services.

    In my case, I only replaced “C:\Program Files\Qlik\Sense\Client\favicon.ico” and “C:\Program Files\Qlik\Sense\Client\img\core\logo\sense-server.png”. For the .png, a simple browser-refresh was all that was necessary to make it show up. For the favicon, I just made an insignificant change to a Virtual Proxy; that causes the Proxy service to reload (and logs everyone out, of course).

    However, the browsers were another story. Firefox 51 showed the new favicon in the list of media for the page, but didn’t switch what it used up in the tab for another minute or so (I never shut down Firefox). Chrome refused to update until after I logged into Qlik Sense (using “Forms” Windows Auth). IE11 never displayed any favicon before or after.

    In my case, I really didn’t care about branding nearly as much as I wanted obvious differentiation for the Dev server.

Leave a Comment

Join us at Living QlikView

Never miss a post.

We Never Spam. NEVER.

Show Buttons
Hide Buttons