Multi-brand operations

Multi-brand workspace

A Brandflux workspace that hosts more than one brand, each with its own DNA, members, campaigns, and DAM. Native to every paid tier, with brand isolation enforced end to end.

Also called: multi-brand, workspace with multiple brands

A multi-brand workspace is a Brandflux workspace that hosts more than one Brand. Each brand has its own DNA, its own members and guests, its own campaigns, and its own DAM. They share billing and seat-management, and nothing else.

Why this is the differentiator

The default shape of a SaaS workspace is one tenant, one brand. Tools built that way force agencies to choose: stand up one workspace per client (multiplied billing, no central member roster), or jam multiple clients into one workspace (no isolation, no client-safe sharing). Brandflux ships with brand as a first-class container inside the workspace. Multi-brand is the default, not a Studio-tier feature flag.

What isolation guarantees

  • Brand DNA isolation. A render against Brand A’s DNA cannot read Brand B’s voice samples, mandatories, or imagery references. The rendering contract enforces this at the constraint layer, not by query filtering after the fact.
  • DAM isolation. Locked masters in Brand A’s DAM are not searchable, listable, or linkable from Brand B’s surfaces. A Lead with access to both brands sees both DAMs, switched explicitly.
  • Guest isolation. A Campaign Collaborator added to Brand A’s campaign cannot see that Brand B exists. The brand-switcher chrome is not rendered for guests.
  • Member isolation. Paid seats can be scoped to specific brands. A Brand A designer doesn’t need to be granted Brand B access to do their job, and the brand list they see reflects only their assignments.

Tier mechanics

The seat and brand counts vary by tier (Freelancer is one brand, Small Team is three, Professional is ten, Studio is unlimited), but the isolation contract is identical at every tier. There is no “lite multi-brand” that leaks across brands at the lower tiers.