Branding Guide Overview

Yurbi provides comprehensive white-labeling and branding capabilities that allow you to customize the interface to match your brand and meet your specific requirements. Whether you're embedding reports into your application, running a multi-tenant environment, or sharing public dashboards, Yurbi's branding features give you control over what users see and how they interact with your data.

What is Branding in Yurbi?

Branding in Yurbi goes beyond just changing logos and colors. It includes:

• Visual customization - logos, colors, favicons, and styling
• Feature visibility - showing or hiding specific functionality
• Custom policies - different branding for different user groups or tenants
• Access control - enabling features for some users while restricting them for others

Prerequisites

Configuring branding requires Admin access to Yurbi.

Understanding the Three Main Use Cases

Yurbi customers typically use the product in three scenarios, each with different branding considerations:

1. Secure Embedding

Reports and dashboards are embedded into your own application or website. Users interact with your product, and Yurbi's reporting capabilities are seamlessly integrated. In this scenario, only the report or dashboard results are displayed - users typically don't see the full Yurbi interface.

2. Direct Login (Multi-Tenant)

Users log directly into Yurbi to access the Dashboard, Library, and Builder sections. This is common in multi-tenant environments where different customer organizations need their own branded experience within the same Yurbi instance.

3. Guest/Anonymous Access

Reports and dashboards are shared publicly without requiring login. These can be embedded on public web pages, shared via direct links, or organized in a Guest Library. Anyone with the link can view the content.

Branding Options by Scenario

Yurbi provides four distinct branding configuration areas:

Login Page Branding

Customize the login page with different branding per domain (perfect for multi-tenant setups) or set a default fallback. This is the first impression users get before they authenticate.

Learn more: Login Page Branding

Guest/Anonymous Branding

Configure the appearance and available features for users accessing reports without logging in. This is a global setting that applies to all anonymous users.

Learn more: Guest/Anonymous Report Branding

Application Branding

Control the interface, features, and appearance for logged-in users. You can create different branding policies for different groups or tenants, allowing you to provide customized experiences or implement tiered feature access.

Learn more: Application Branding (Logged-in Users)

Embedded Content Branding

Fine-tune what features are available when reports and dashboards are embedded. You can configure embedded content differently than the full application - hiding complexity in embeds while exposing more power to users who access the full interface.

Learn more: Embedded Report and Dashboard Branding

Key Capabilities

Per-Tenant or Per-Group Branding

Create multiple branding policies and assign them to specific user groups or individual users. This is powerful for:

• Multi-tenant SaaS products - Each customer organization sees their own branding
• Tiered pricing models - Enable premium features only for certain customer tiers
• Department-specific views - Customize the interface based on user roles

Feature Control

Beyond appearance, branding allows you to show or hide functionality such as:

• Export and print capabilities
• Scheduling and email options
• Dashboard editing tools
• SQL view access
• Embedding and anonymous sharing options

Advanced Customization

All branding sections include options for Custom CSS, Custom JS, and Custom HTML, giving you unlimited flexibility to extend Yurbi's appearance and behavior.

Important: When Branding Changes Take Effect

For Application Branding (logged-in users): Branding policies are applied when a user logs in. To see changes after updating a branding policy, users must log out and log back in.

For Guest and Login Page Branding: Changes take effect immediately since these apply to non-authenticated pages.

Global Settings

Some branding elements are global and affect all users:

• Product Name (Settings → Server Settings → Application Settings) - Controls the page title for all logged-in users
• Guest Branding - A single policy applies to all anonymous users
• Default Login Page Branding - Serves as fallback when no domain-specific policy exists

Getting Started

We recommend configuring branding in this order:

1. Set your Product Name in Server Settings to establish the basic identity
2. Create your Default Login Page Branding so users see your brand from the start
3. Set up Guest Branding if you're sharing any public reports or dashboards
4. Create Application Branding policies for different user groups or tenants
5. Configure Embedded Branding if you're embedding content into other applications

Additional Resources

Report Headers and Footers: You can also customize the header and footer of exported and scheduled reports on a per-report basis. Learn more in our How to Add and Configure Report Headers article. Note: In an upcoming release, you'll be able to set default headers/footers through branding policies.

Best Practices: See our Branding Best Practices and Common Scenarios article for recommendations on multi-tenant setups, tiered pricing strategies, and troubleshooting.

---

Need help with branding? Contact our support team or check out the specific articles above for detailed configuration instructions.