Skip to content

Brand Style Presets

Brand style controls define reusable guidance for how generated outputs should look and align to governance expectations.

Brand style guidance can include visual direction such as:

  • “Cinematic lighting, dark blue and gold colour palette, no text overlays, photorealistic” — for video slides.
  • “Clean white background, blue and grey corporate colour scheme, minimal design” — for infographics.

These controls are applied through brand profile and policy workflows.

Brand controls can affect these generation areas:

TargetUsed In
VideoVisual direction for generated scenes and slides
InfographicVisual style for infographic output
Slide DeckTemplate and design constraints for deck workflows
Image RegenerationBrand-consistent visual refinement passes

Use Brand Controls to manage active brand behavior:

  1. Create or select a brand profile draft.
  2. Configure style, policy, and standards scan fields.
  3. Validate rules or run a standards scan.
  4. Activate the selected profile.

If your team maintains an external brand standards site, use Brand Standards Scans to bring source-backed guidance into the profile editor before activation.

For stable team operations:

  • Treat customization changes as controlled updates, not one-off experiments.
  • Record intent for major prompt/brand/policy adjustments so teams can audit behavior over time.
  • Roll out changes to a smaller pilot group before broad adoption.

If custom behavior appears inconsistent:

  • Confirm the active profile/template/version is the one you intended to use.
  • Validate that project-level settings do not override global defaults.
  • Re-test using a known baseline input to isolate whether the issue is configuration or content related.

Start with global baselines, then add team-level tuning only where business goals clearly differ.

How often should we revise prompt or brand settings?

Section titled “How often should we revise prompt or brand settings?”

Use a cadence (for example weekly or bi-weekly) tied to measurable quality outcomes.

Version changes, test against known examples, then promote after reviewer sign-off.