White-labelling Omniscope: Building a custom app with own branding

Modified on Fri, 19 Apr 2024 at 03:48 PM

Omniscope provides an extensive array of tools for crafting bespoke data solutions, empowering your company or clients with invaluable insights encapsulated within a single application.

With the Evo Enterprise license, users can insert their own company branding into this tailored solution or opt to incorporate the client's branding into the navigation pages and distributed reports.

While some application menus and interfaces may still bear references to Omniscope's support and help pages, or display the application / vendor name, these can be easily eliminated or replaced using the advanced white-labeling option. This optional feature can be added to the standard Evo Enterprise commercial package.

(Pricing information is available upon request.)

This guide offers comprehensive instructions on how to activate branding and white-labeling options, and remove all mentions of the Omniscope application and its vendor, Visokio.

The changes need to be applied across two specific segments and interfaces.

Projects Page Branding

On the Projects page, on the root folder, open the 3-dot menu in the top right hand corner and pick 'Edit Branding'.

"Styles" options along the top allow the user to create and apply the custom colours to the application pages, menus, buttons and data; add logos, images and change the application font.  At the bottom of this menu page the users can find options to export the whole newly-created style bundle, or import a bundle that someone else created (as an ilf file).


Some of the options below are shared with the standard branding functionality, while some will be white-label specific.

Admin > App branding and naming

This is the second area where further customisation will take place. The options below will by default show Omniscope Evo as the application name and Visokio as the vendor. 

This is the Admin menu where the author can apply another application's name and the associated organisation name. 

Further options are white-label specific and deal with translation and custom search-replace app wording, so the user experience can be completely tailored to lead the end user to the new company's website or support pages. 

(see under 'Custom replacements')


We support the addition of a customisation.css file within the branding.internal folder for style overrides and visual component hiding.

For example, inserting this rule will hide the Device / Filter titles:
div.device-header-section.horizontal.layout { display: none; }    

N.B. You can easily obtain these rules by inspecting the elements in the browser dev console.

WARNING: We do not guarantee the seamless transition of your customisation.css from one version to another due to potential CSS structure changes. It's highly recommended to thoroughly test your customisation.css before deploying to production when upgrading to a newer version.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article