When your customers log into the OpenCX dashboard through an org you created, they see your brand instead of OpenCX’s default branding.
What’s customizable
| Element | Where it appears | Field |
|---|
| Logo | Sidebar header (collapsed and expanded states) | logo_url |
| App name | Browser tab title (replaces “Open”) | app_name |
| Support email | All “contact us” links and error messages across the dashboard | support_email |
| Primary color | Reserved for future use (v2) | primary_color |
How it works
Branding is configured on your partner record — not on individual orgs. Every org you create inherits your branding automatically.
Configuration
Branding fields are set on your partner record during onboarding. Contact the OpenCX team to update them.
| Field | Type | Example |
|---|
logo_url | URL to your logo image (SVG or PNG recommended, square aspect ratio) | https://cdn.example.com/logo.svg |
app_name | Name shown in the browser tab | "Booking Support" |
support_email | Email shown in all “contact us” copy | "[email protected]" |
primary_color | Hex color code (reserved for v2) | "#003580" |
Use a square logo (1:1 aspect ratio) for best results. The logo renders at 32x32px in the sidebar. SVG is preferred for crisp rendering at all sizes.
What’s not branded (v1)
These elements currently show OpenCX defaults regardless of partner configuration:
- Login page — The auth page loads before any org context is available. Branding kicks in after login.
- Invitation accept page — Same constraint as login.
- Favicon and Open Graph image — Static assets that require per-domain serving.
- Primary color theming — Changing
--primary also requires computing a contrast-safe --primary-foreground. Deferred to v2.
Billing
For partner orgs, the Billing page is automatically hidden from the settings navigation and command palette. Partners handle billing with their customers directly — OpenCX bills the partner at the account level. 