White-labeling

Organization white-labeling sets the logo, colors, and links shown inside your organization's workspaces. Authorized external workspace members also see the workspace's organization branding. Public login, manifest, and file-share surfaces use the separate instance-wide branding baseline.

Organization owners and admins configure white-labeling. Billing-enabled deployments require Enterprise. On billing-disabled deployments, organization white-labeling defaults on; explicit WHITELABELING_ENABLED=false and NEXT_PUBLIC_WHITELABELING_ENABLED=false disable it. See self-hosted enterprise setup.

Configure organization branding

Open Settings → Organization → White-labeling.
Set identity, colors, and links using the fields below.
Click Save. Refresh other open tabs to pick up changes.

Identity

Field	Use and limit
Logo	Square image in the collapsed sidebar. PNG, JPEG, SVG, or WebP; maximum 5 MiB.
Wordmark	Wide image in the expanded sidebar and loading screens. Same formats and 5 MiB limit.
Brand name	Sidebar and selected UI labels; maximum 64 characters.

Loading screens use the wordmark rather than the square logo. Without a wordmark, they use the brand name; the default name Sim uses the built-in Sim wordmark.

Colors

Use valid hex values, such as #701ffc.

Field	Use
Primary color	Buttons and active states.
Primary hover color	Hover state for primary elements.
Accent color	Highlights and secondary interactive elements.
Accent hover color	Hover state for accent elements.

Links

Field	Use
Support email	Help prompts; must be a valid email address.
Documentation URL	Documentation link.
Terms of service URL	Terms link.
Privacy policy URL	Privacy link.

The URL fields require valid URLs. Check the collapsed and expanded sidebar, a loading screen, and the support/legal links after saving.

Scope and fallback

Saved organization values override the instance baseline inside that organization's workspace. Clearing an organization value restores the corresponding instance or Sim default. The settings read requires organization membership; updates require an owner or admin. Workspace visitors receive branding through their authorized workspace context.

Organization branding does not replace the signed-out login identity, PWA manifest, or public file-share identity. Those surfaces read instance settings. The manifest retains built-in icons; public file shares hide the Sim wordmark when an instance logo is configured rather than rendering a custom wordmark there.

Instance-wide branding

Instance settings need no organization or WHITELABELING_ENABLED. They supply a deployment baseline and reach signed-out surfaces as well as workspace fallback values. Set the environment variables on your self-hosted app and apply them through your deployment's update process.

Identity variables

NEXT_PUBLIC_BRAND_NAME=Acme
NEXT_PUBLIC_BRAND_LOGO_URL=/branding/logo.png
NEXT_PUBLIC_BRAND_WORDMARK_URL=/branding/wordmark.svg
NEXT_PUBLIC_BRAND_FAVICON_URL=/branding/favicon.ico
NEXT_PUBLIC_CUSTOM_CSS_URL=/branding/custom.css

Favicon and custom CSS have no organization-setting equivalent. Asset URLs reference files; they do not upload them. Custom CSS must be same-origin under the current style-src policy, which permits the app origin and Google Fonts rather than configurable external stylesheet hosts.

Color variables

NEXT_PUBLIC_BRAND_PRIMARY_COLOR="#701ffc"
NEXT_PUBLIC_BRAND_PRIMARY_HOVER_COLOR="#6518e6"
NEXT_PUBLIC_BRAND_ACCENT_COLOR="#9d54ff"
NEXT_PUBLIC_BRAND_ACCENT_HOVER_COLOR="#8c3dff"
NEXT_PUBLIC_BRAND_BACKGROUND_COLOR="#0c0c0c"

NEXT_PUBLIC_BRAND_BACKGROUND_COLOR helps choose contrasting text for your brand's background. It does not paint the application background and has no organization equivalent.

Link variables

NEXT_PUBLIC_SUPPORT_EMAIL=support@acme.com
NEXT_PUBLIC_DOCUMENTATION_URL=https://docs.acme.com
NEXT_PUBLIC_TERMS_URL=https://acme.com/terms
NEXT_PUBLIC_PRIVACY_URL=https://acme.com/privacy

Setting the brand name, logo URL, wordmark URL, or primary color marks the deployment as branded. The other values refine its appearance and links.

Serve assets on Kubernetes

The Helm chart can mount branding files into the app's public directory:

branding:
  enabled: true
  mountPath: /app/apps/sim/public/branding
  files:
    wordmark.svg: |
      <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 120 24"><text y="18">Acme</text></svg>
  binaryFiles:
    logo.png: "<base64-encoded PNG>"
    favicon.ico: "<base64-encoded ICO>"

Use plain text for CSS, JSON, or SVG in files; use base64 for PNG, JPEG, or ICO in binaryFiles. Replace the example binary placeholders with the actual encodings. With the default mount path, logo.png is served at /branding/logo.png.

Outside Helm, serve the assets yourself and use URLs reachable by your users' browsers and allowed by your deployment's content security policy. Keep custom CSS same-origin. Verify signed-out login and a public file share separately from the organization's workspace.

White-labeling

On this page