Trust

Private customer rooms need clear boundaries.

BexBrand should keep buyer-facing material tied to approved sources, access rules and human approval.

Data

What BexBrand should hold

The product stores brand and customer context because that is the value of the workflow.

Core

Guidelines, URLs, Figma links, logos, PDFs and notes need explicit account ownership.

Core

Rooms store buyer-facing assets and access rules for named customer teams.

Core

Views, opens and access requests should be visible to the account team.

Controls

The trust posture is strongest when generated material cannot drift away from review.

Required

Customer access should be scoped, expiring and traceable.

Required

Published assets need approval before customer-facing use.

Required

Generated drafts should respect account-level AI budget limits.

Shared app

The consolidated dashboard makes it clear who can use Bex and which account owns the work.