Approval rounds and version history

Every variation in Brandflux moves through a small state machine: draft, in review, changes requested, approved. Version history persists across the full path.

The approval states

• Draft. The designer is still iterating. Reviewers do not see drafts.
• In review. Visible to all assigned reviewers (internal and guest). Comments thread on each variation.
• Changes requested. A reviewer asked for a specific change. The variation moves back to the designer’s queue. The original is preserved as version N; the new attempt becomes version N+1.
• Approved. Required-approver roles signed off (configured per workspace on Professional and Studio).
• Ship-ready. Approved and exported. Branded-surface rules apply on Studio and above.

How iterations count toward credits

Every regenerate is a new credit charge. A 1K variation regenerate costs 1 credit; a 4K regenerate costs 5 credits. Nudging a DNA field and re-rolling is one credit per resulting variation.

What does not count: comments, approval state changes, exports, link sharing, version-history viewing. Credits are spent only when the model produces new pixels or new copy.

Version history

Every variation keeps the full lineage. Click any version in the side rail to view the prompt, DNA snapshot, and reviewer comments at that moment. The lineage is exportable as a JSON or PDF for compliance review or client handover.

Required-approver roles

On Professional, set required-approver roles per workspace from settings. The default lets anyone with seat access approve; agencies typically restrict this to creative director or principal. Studio adds per-brand approver overrides for shops with brand-specific sign-off chains.

Next: API and webhooks for Studio teams running Brandflux from their own tools.