Branding & white-labeling

Most of what makes Yurbi look like your product isn't done through the API — it's configured in Branding profiles. Here's what you can control, and where each piece lives.

For an embedding vendor, branding is half the integration: it's how Yurbi stops looking like Yurbi and starts looking like your product. Most of it is configured in the Branding area of the Yurbi admin, and it can also be automated through the API when you provision tenants at scale. It's extensive — logos, colors, fonts, which features are visible, the login page, public views, and the embedded experience. Branding profiles can apply to all users, a specific group, or a specific user, which ties directly into how you provision groups for multi-tenant setups.

This page is a map; each link goes to the full guide in the Yurbi knowledge base.

Where to start

• Branding Guide Overview — the white-labeling capabilities at a glance, and how branding profiles work.
• Branding Best Practices & Common Scenarios — practical patterns for multi-tenant environments and tiered (per-plan) feature sets.

The four surfaces you can brand

• Application Branding (logged-in users) — the full experience for users who log into Yurbi (Dashboard, Library, Builder): appearance plus which features each audience can see.
• Embedded Report & Dashboard Branding — the most relevant for embedding: fine-tune exactly which features appear inside an embed, so you can ship a clean, simplified view in your app. Pair this with the Embedding guide.
• Login Page Branding — a branded (optionally per-tenant) login experience, when users hit Yurbi directly rather than via single sign-on.
• Guest / Anonymous / Public View Branding — control appearance and available features for public, no-login content.

Automating branding

Branding profiles can be created and assigned through the API, which is how a multi-tenant deployment gives each customer their own look without an administrator configuring it by hand. The Branding endpoints cover creating a profile, assigning it to groups and users, activating it, and uploading logo and background images.

A typical tenant onboarding creates the branding profile alongside the tenant's security group, then assigns the profile to that group so every member inherits it. See Multi-tenant provisioning for where this fits in the wider sequence.

Going beyond the settings

When the built-in options don't reach a specific element, Branding profiles include a Custom CSS area. That's how you match fonts, spacing, and component styling exactly to your app — see the Custom CSS guide.

Tiered products: because a branding profile can be scoped to a group, you can map profiles to your own plan tiers — e.g. "Basic" sees an embedded dashboard only, "Premium" gets the builder and scheduler — all without code.