Multi-brand groups, franchise networks, and shared services teams all ask the same question in the same word. Here is what each surface actually carries today, the route where your brand is the only one on the page, and the half of the question that creates real exposure.
Thematic ships one workspace-level branding control: a logo and organization details that appear in the portal title bar and in emails. There is no color theming, no custom domain, and no per-brand logo, and anything beyond that is handled case by case. The route to a report carrying only your brand is the Power BI connector or a warehouse export into a surface you already own, and the question worth settling first is which rows each recipient may see.
A retail group with six banners wants each brand team to open a report that looks like their brand, not like a vendor's. A franchise network wants every location to see its own numbers and not the store down the road's. A shared services team wants to hand 40 business units something they'll actually read. All three ask roughly the same question, and all three use the same word for it.
Partially, and the split matters. Thematic ships one workspace-level branding control: an admin can upload a logo and set the organization name, and that logo appears in the portal title bar and in emails. There's no color theming, no custom domain, and no per-brand logo. One workspace carries one logo. Anything past that is handled case by case rather than as a packaged offering, and the fastest route to a report carrying only your brand isn't a branding setting at all. It's moving the data into a surface you already own.
"White-label" bundles at least four different asks, and in feedback analytics the branding half is usually the easier half. Below is what each surface actually carries today, the route where your brand is the only one on the page, and the part of the question that creates real exposure.
Separate the asks before scoping anything. Vendors answer them very differently, and buyers rarely say which one they mean.
Two related terms get used interchangeably and shouldn't be. Embedded analytics answers "where does it live," meaning inside an application rather than a separate tool. White-labeling answers "whose brand does it carry." The two are independent: a fully branded standalone portal isn't embedded, and an unbranded frame inside your own app is embedded but not white-labeled. Gartner Peer Insights' market definition of embedded analytics says nothing about branding at all. That's a fair sign the conflation belongs to buyers rather than to the category.
Depth also decides the commercial shape. Logo and theme settings are usually configuration. Custom domains, sender identity, and per-tenant branding are usually provisioning plus a contract term. Looker's Private Label option has to be enabled by Google Cloud for your instance, with pricing through a sales conversation. Zoho Analytics documents its white-label BI as available on request, with the domain fixed at provisioning and changeable only by writing to support. In partner terminology, a white-label partner resells a vendor's complete standalone product under its own brand, while an OEM partner incorporates the technology as a component of its own. Neither is a settings toggle.
| Surface | What carries your brand | What doesn't |
|---|---|---|
| Portal title bar | Your uploaded logo and organization name | The product interface itself, and the platform address |
| Emails from the platform | Your workspace logo | The sender address; shared Answers send from a Thematic support address |
| Exports (PowerPoint, PNG, CSV) | Your filters, metadata, and data | Export-level brand templating is not a configurable feature today |
| Power BI and warehouse destinations | Everything, because Thematic renders nothing there | Nothing; you own the visualization layer |
Three limits worth stating plainly. The logo is set per workspace, so a group wanting a different logo per brand would need separate organizations, and organizations are a billing unit. There's no public sharing: link sharing is read-only inside the organization, and anyone opening a linked dashboard needs an account, though not a paid seat. And the regional addresses that exist (EU and ANZ) are data residency options, not branding ones.
The cleanest answer to the branding question isn't a branding feature. It's moving the analysis into a surface you already control.
Thematic ships a Power BI data connector, distributed as a .mez file for Power BI Desktop. It exposes themes as rows carrying name, count, base score, impact, and sentiment, navigable by organization, survey, and data source. Because it's a data connector rather than a visual embed, Thematic renders nothing. Your analysts build the report in your workbook, on your template, and the output carries your branding by default rather than by configuration.
The same logic covers the warehouse route. Thematic supports recurring automated exports to SFTP, Snowflake, and BigQuery, per dataset and on a schedule, with configurable columns and full or changed-only modes, plus write-back to Microsoft Dynamics. Once themes and scores are rows in your warehouse, whatever your reporting layer draws is yours.
The trade-off is worth naming. You're getting structured theme data, not a finished visualization. You inherit the design control and the design work at the same time.
For a multi-brand group, "can you white-label it" is usually standing in for something sharper: can I hand brand X a report that looks like brand X's and contains only brand X's data. Branding is the visible half. Permissions are the half that creates exposure.
The governance principle from embedded analytics applies directly. Enforcement belongs at the data layer, not the presentation layer. A filter applied at query time based on who is asking, which the viewer cannot remove, is a permission. Hiding a chart is not. The canonical multi-unit requirement is simultaneous roll-up and isolation: corporate sees the whole network and can drill into any location, while each location sees only itself, usually for competitive-territory reasons. Roll-up only holds if the metric means the same thing in every brand, which is its own problem to solve.
This is where Thematic is considerably stronger than it is on branding. Lens Views create tailored perspectives on one underlying Lens for different teams or regions without duplicating setup, and they carry always-on data restrictions that view users cannot disable, plus minimum row requirements. Each view gets its own shareable URL. Underneath, permissions run per dashboard and per dataset, with four default roles, custom per-user permissions, SAML 2.0 single sign-on, just-in-time provisioning, and System for Cross-domain Identity Management (SCIM) v2 for user lifecycle management.
A perfectly branded dashboard that leaks a sibling brand's scores is a worse outcome than a plain one that doesn't.
The working pattern is to generate the analysis in Thematic and deliver it inside your own template.
Community Health System, a not-for-profit healthcare network serving California's central San Joaquin Valley, runs an annual employee engagement survey across 250 departments. Its Organizational Development team built one dashboard template in Thematic with the same layout for every department, applied a department filter, and copied the outputs into their own Canva template. That produced 250 one-page reports in a single three-day sprint. Preparation dropped from roughly an hour to about 20 minutes per department. The team saved more than 160 hours and over $10,000 per reporting cycle. "We were able to reach 250 departments," said Alexandra Clifton, Organizational Development Partner. "Yes, it was a lot of work, but it was all front-loaded to a single three days." Every recipient got a one-pager in the organization's own design system.
Distribution can also stay in-platform when the audience is internal. Greyhound is the bus network operating across the United States, Canada, and Mexico. Its post-trip customer survey feedback reaches station managers, who check their own station's dashboard once or twice a week. "Thematic allows us to identify issues and distribute them to our station managers in real time," said Matthew Schoolfield, Manager for Commercial Analytics. "Before, when we sent the reports out, we were just hoping that people will read them, but had no way of telling." A multinational food and beverage producer with revenue over $10 billion and more than 20,000 employees runs self-service employee engagement insights across eight business units and hundreds of sites, saving $170,000, the equivalent of 180 hours a month. Mitre 10 covers 84 stores and 20,000 verbatim comments a month with a three-person insights team.
Two mechanics make the pattern repeatable. Dashboards can be downloaded as templates and recreated in another portal through a mapping wizard, which is how one layout gets stood up across many brands or business units. And email digests go to a subscriber list weekly, monthly, quarterly, or annually, skipping any cycle where no new data has loaded.
Partially, and precisely. Thematic gives you a workspace logo and organization details that show in the portal and in emails. It does not give you color theming, a custom domain, per-brand identities, or vendor-name removal, and export-level brand templating is not a configurable feature today. Anything beyond the workspace logo is handled case by case rather than bought off a page. If the requirement is that the finished artifact carries only your brand, the shipped route is the Power BI connector or a warehouse export into a surface you already own. And the question to settle before any of it is not whose logo sits in the corner. It's which rows each recipient is allowed to see.
Thematic turns fragmented feedback into one consistent source of customer truth — so every team acts on the same customer story. Up and running in days, not quarters.
Transforming customer feedback with AI holds immense potential, but many organizations stumble into unexpected challenges.
