Creating Brand Profiles

Brand Controls lets administrators and brand managers define reusable governance profiles for generation.

What A Brand Profile Includes

A profile can include:

Brand identity settings
Logo and watermark constraints
Color and style guidance
Policy rules used for validation and preview

Profile Lifecycle

Brand profile workflow follows a draft-to-active model:

Create a new draft profile.
Configure profile fields and standards source settings.
Validate rule sets.
Save profile updates or run a standards scan.
Activate selected profile.

Only one profile is active at a time for active brand governance behavior.

Exporting And Importing Profiles

Brand Controls now supports portable profile bundles so you can move a complete brand setup to another machine or environment.

Use the actions in the Brand Controls header:

Select a saved profile and choose Export Selected to download a .zip bundle.
Choose Import Profile to upload a bundle created by the export action.

The bundle includes:

Profile metadata and rule settings
Uploaded logo assets referenced by the profile
Slide deck templates assigned to the profile
Custom template-studio layouts saved into the profile
Template images referenced inside saved slide templates

Imported profiles are created as drafts even if the source profile was active. This gives you a chance to review the imported settings, templates, and assets before making the imported copy active in the destination environment.

If you import the same profile more than once, Brand Controls keeps each imported copy as a separate profile so you can compare or rename them safely.

When a profile is no longer needed, select it in Brand Controls and use Delete Profile. Deleted profiles are archived and removed from the Brand Controls list so they can no longer be activated or selected for future work.

Standards Scan Workflow

Brand Controls can now compare a profile against an external standards source and write approved updates back into the profile editor.

Use this when you want the platform to help align your profile with a published design or brand standards site.

What You Can Configure

The source label and source URL
Whether the profile uses a lighter heuristic scan or the deeper agent-assisted scan
How many pages the scan can inspect
Which domains or URL patterns are allowed or excluded
The minimum confidence needed before extracted guidance is applied

What Happens During A Scan

When you select Run Scan Now:

Any unsaved profile changes are saved first.
The platform checks the configured standards source.
Matching palette, typography, and prompt-guardrail guidance is compared against the current profile.
Approved changes are written back into the editor so you can review them in the relevant sections.

What You Will See After A Scan

The compliance area shows:

Last scan mode
Pages scanned
Evidence trail for extracted guidance
Delta and applied-change summaries
Any source or scan errors that need attention

This makes it easier to verify why a profile changed before you activate it.

Permissions

Brand Controls are restricted to admin and brand manager roles.

Governance And Change Control

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.

Troubleshooting

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.

Frequently Asked Questions

Should we optimize globally or per team?

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

How often should we revise prompt or brand settings?

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

What is the safest rollout strategy?

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