White-Labeling¶

Overview¶

White-labeling allows you to customize the appearance of Actian Data Intelligence Platform applications with your organization's branding. You can replace selected branding elements to create a consistent experience for your users while preserving standard platform functionality.

White-labeling is supported for the following applications:

• Studio
• Explorer
• Administration

You can apply your branding across all supported applications or to individual applications, depending on your requirements.

This document describes the branding inputs required to create a high-quality branded experience.

Supported Customizations¶

The following branding elements can be customized as part of white-labeling:

The following illustration shows the branding elements that you can customize across supported applications, including the application logo, favicon, browser page title, and primary brand color.

The following illustration shows the branding elements that you can customize on the Explorer homepage, including the application logo, heading font, and background image.

Branding Inputs¶

Provide the following branding assets and text inputs based on your requirements.

Required Assets¶

• Application logo
• Favicon
• Primary brand color

Optional Asset¶

• Explorer homepage heading (H1) font

Required Text Inputs¶

• Browser page title text: Text displayed in the browser tab and window title.

• Application names: Text used in application navigation and actions, for example, Open in <custom Studio name>.

  Important

  Application names and Browser page title text must not contain the characters &, <, or >. Use spelled-out words instead (for example, use and instead of &).

• Support URL: The URL used for support links within the applications. If not provided, the default Actian support URL is used.

Asset Specifications¶

All assets must meet the following specifications for approval.

Application Logo¶

You can use a single logo across all applications or provide application-specific logo variants. Application-specific logos should maintain a consistent visual identity while adapting colors or backgrounds when necessary.

Logo Specifications¶

Additional Requirements¶

• Logos must remain legible at small sizes, such as in headers and loading screens.
• If a logo cannot maintain sufficient clarity at small sizes, provide a simplified variant.

Favicon¶

Favicons are displayed in browser tabs and bookmarks.

You can provide a single favicon for all applications or application-specific favicons, depending on your requirements.

Favicon Specifications¶

Primary Brand Color¶

You can provide one primary brand color for your organization. The platform derives the required color shades from your primary brand color to support UI states such as hover, active, and disabled, while maintaining consistent theming across the platform.

Color Specifications¶

Color Limitations¶

• Gradients and secondary color palettes are not supported.
• Color adjustments might be recommended if the selected color affects accessibility or usability.

Font¶

You can customize the font used for the Explorer homepage heading (H1) only. All other platform text uses the default Roboto font.

Font Specifications¶

Email Branding¶

Email branding supports limited customization through webhook integration. For more information about configuring webhooks, see Managing Notifications.

Supported branding elements include the logo and primary brand color.

For more information, contact your Customer Success Manager (CSM).

Package and Submit Branding Assets¶

Provide all branding assets in a single ZIP archive using the following folder structure.

Folder Structure¶

white-labeling-assets/
│
├── logos/
│   ├── studio-logo.svg
│   ├── explorer-logo.svg
│   └── admin-logo.svg
│
├── favicons/
│   └── favicon.svg
│
├── fonts/
│   └── explorer-h1.ttf
│
└── brand-color.txt

Asset Validation and Review¶

Submitted assets are reviewed to ensure they meet the specifications in this document, including:

• Completeness against the specifications in this document
• Visual clarity at the required formats and sizes
• Accessibility and contrast compliance
• Consistency across applications

After implementation, a branded version of the platform may be shared with you for review and approval.

Unsupported Customizations¶

The following customizations are out of scope for white-labeling:

• Custom UI layouts or structural changes
• Multiple themes within a tenant
• Custom icons other than logos and favicons
• Email template redesign or copy customization
• Application behavior or feature changes

Requests outside this scope require separate review and agreement.