Skip to main content
Version: Developer

Custom Branding

Overview

Kasm Workspaces lets administrators replace the default look with custom branding that reflects an organization's identity. This guide configures application branding, which controls logos, login text, and backgrounds based on the hostname users access, and session branding, which controls the desktop background inside a workspace. A branded deployment presents a consistent, professional experience to users and external audiences. As a result, the platform feels like an extension of the organization rather than a generic tool.

Default Branding
Default Branding
Custom Login Logo Caption and Splash
Custom Login Logo Caption and Splash
Workspaces launcher supports using a custom background
Workspaces launcher supports using a custom background

Prerequisites

Before you begin, confirm the following:

  • Administrator access to the Kasm Workspaces deployment, with permission to manage branding settings.
  • Application branding requires Kasm Workspaces Enterprise.
  • Hosted image URLs for any custom logos, favicons, and backgrounds you intend to use. Favicon images must be square so that the progressive web app (PWA) is installable.
  • For session branding, the ability to build a custom image or apply file mappings. See Building a Custom Image and Using File Mapping to Change the Default Background of a Workspace.

Solution approach

This guide progresses through the following phases:

  1. Configure application branding per hostname.
  2. Configure session branding for the workspace background.
  3. Reference the available default backgrounds.

Detailed steps

Configure application branding

Kasm Workspaces lets administrators define multiple branding configurations. The system selects a configuration based on the URL hostname the user accesses the deployment with.

info

Application branding is available in Kasm Workspaces Enterprise.

  1. In the Kasm Workspaces UI, go to Settings > Branding.
  2. Review the existing branding configurations in the list.
Branding Config List
Branding Config List
  1. Add a new configuration or edit an existing one to open the branding options.
Branding Options
Branding Options
  1. Set the fields described in the following table, then save the configuration.
NameDescription
NameThe name for the configuration.
HostnameThe hostname of the URL used to access the Kasm deployment is used to map the appropriate branding config.
Favicon Logo URLURL for the favicon logo image, this image is also used for the global PWA icon, icons must be square for the PWA to be installable.
Admin Dashboard Logo URLURL for the logo shown in the sidebar on the admin pages.
User Dashboard Logo URLURL for the logo shown on the user dashboard, this is often the same as the admin dashboard logo, but doesn't have to be.
Launcher Background URLURL for the background image for the Workspaces launcher. See Default Backgrounds for a list of available default images.
HTML TitleHTML document title, this is also set as the global PWA title.
Login CaptionCaption displayed under the login logo.
Login Logo URLURL for the login logo image. If a custom logo is used, the phrase "Powered By Kasm" will be displayed under the new logo.
Login Splash Background URLURL for the login splash background image.
Username Input LabelLabel for the username input field on the login page.
Loading Session TextThe text to display while the user is connecting to a session.
Joining Session TextThe text to display while the user is joining a shared session.
Destroying Session TextThe text to display when the session is being destroyed.
DefaultIf the configuration is set to Default, this system will use this configuration if the URL hostname does not match another config.
tip

Changes to branding may take up to 90 seconds to apply, because the system caches certain requests. When you regularly change and test branding settings, use the following steps to observe the changes:

  1. Wait 90 seconds after you make the configuration change.
  2. Log out of the Kasm UI.
  3. Navigate the browser to the login page, then do a hard refresh of the page. A hard refresh is typically CTRL+F5. Alternatively, clear the browser cache.
  4. Log in and verify the changes.

Configure session branding

Session branding controls the desktop background shown inside a workspace container. Change the default background by Building a Custom Image or Using File Mapping to Change the Default Background of a Workspace.

  1. Prepare a replacement background image. The recommended resolution is 1920x1080 px.
  2. Replace the following file inside the image:
/usr/share/backgrounds/bg_default.png
  1. To brand casting links, set the Launcher Background URL on the casting page.

Reference default backgrounds

Workspaces includes a number of default backgrounds. The following previews show each image and the relative URL you can use in the configurations.

img/backgrounds/background1.jpg
img/backgrounds/background1.jpg
img/backgrounds/background2.jpg
img/backgrounds/background2.jpg
img/backgrounds/background3.jpg
img/backgrounds/background3.jpg
img/backgrounds/background4.jpg
img/backgrounds/background4.jpg
img/backgrounds/background5.jpg
img/backgrounds/background5.jpg
img/backgrounds/background6.jpg
img/backgrounds/background6.jpg
img/backgrounds/background7.jpg
img/backgrounds/background7.jpg
img/backgrounds/background8.jpg
img/backgrounds/background8.jpg
img/backgrounds/background9.jpg
img/backgrounds/background9.jpg
img/backgrounds/background10.jpg
img/backgrounds/background10.jpg
img/backgrounds/background11.jpg
img/backgrounds/background11.jpg
img/backgrounds/background12.jpg
img/backgrounds/background12.jpg

Common troubleshooting steps

  • Branding changes do not appear. The system caches certain requests, so changes may take up to 90 seconds to apply. Wait 90 seconds, log out, hard refresh the login page with CTRL+F5 or clear the browser cache, then log in again.
  • The wrong branding configuration loads. The system maps a configuration by the URL hostname users access. Confirm that the Hostname field matches the access URL. Set one configuration as Default to cover hostnames that match no other config.
  • The PWA does not install with the custom favicon. The favicon image must be square. Replace the Favicon Logo URL image with a square version.
  • The Branding settings are unavailable. Application branding requires Kasm Workspaces Enterprise. Confirm the deployment license includes Enterprise features.
  • The custom session background does not display. Confirm that the replacement image overwrites /usr/share/backgrounds/bg_default.png in the workspace image, or that the file mapping targets that path.