Summary

The Brand Compliance Agent validates every asset against your brand guidelines and regulations, so the world's most ambitious brands can accelerate their content operations, scale further and show up consistently, without ever compromising the brand they've built. 

The Brand Compliance Agent learns your exact brand rules; logo placement, color palettes, messaging, templates and enforces them at scale, flags non-compliant regulations specified by you, claims, offers, technical specs and forbidden objects and checks against multiple rulesets tailored to specific brands, regions, channels or marketing campaigns.

Who?

• DAM administrators and brand managers: define, update, and manage compliance rulesets for the organization.
• Content creators and uploaders: add assets to the DAM and get immediate feedback on whether their content meets official company standards.

Prerequisites

Before you create your first Brand Compliance Agent:

1. Set up a compliance metaproperty. In your taxonomy, create a new metaproperty (any name you like) as a single-select field with four options: ‘Compliant’, ‘Non Compliant’, ‘Partially Compliant’ and ‘Not Applicable’. The agent writes its results here.
2. Have your brand guidelines and regulations ready. You'll turn these into precise, objective rules, see How to Write A Good Brand Rule for the full guide.
3. Check your permissions. Building and editing rulesets requires Manage Agents. Running the agent on assets requires Run Agents. Reviewing and approving the agent's proposed compliance status also requires Manage Agents (see Reviewing your results below).

What it checks

The agent evaluates each asset against your rules, grouped into categories you control. For example:

How it checks

Behind every rule you write, the agent draws on a growing set of detection techniques, and we're continually improving their accuracy and depth. Among them, for example, we look at:

This isn't an exhaustive list. We're actively expanding what the agent can detect, so if you're not sure whether a specific check is supported, ask your Bynder contact rather than assuming it isn't.

Why use it?

• Protect your brand. Stop off-brand, inconsistent, outdated, or non-compliant files from entering your active asset library.
• Move at the speed of your markets. Customize rulesets for regional teams or time-sensitive promotions without rebuilding from scratch.
• Scale past manual review. Content demand outgrows what a brand team can check by hand. The agent reviews at whatever volume you need.

How?

Create your Agent

1. Navigate to the Agent Library via Settings > AI Agents > Manage AI Agents.
2. Click Create agent and select Brand Compliance.
3. Add your categories and rules, derived from your brand guidelines and regulations. Keep each rule precise and objective so the agent can evaluate it as consistently as possible. See How to Write A Good Brand Rule.
4. Select the metaproperty you set up in Prerequisites to map the agent's output to.
5. Add a Name and Description, then click Create Agent.

Keep in mind:

• You can reference one rule from another within the same category, but not across categories. A color definition set up in one category can't be referenced by a rule in a different category, repeat the definition where you need it.
• The agent respects your Global AI Instructions, so compliance checks stay aligned with your brand tone and terminology.
• Group related rules into one category rather than spreading them thin, it keeps cross-referencing simple and your ruleset easy to maintain.

Add a Reference Asset to a Rule

If a rule needs a visual reference, such as your logo file, attach it:

1. Select an asset under Attachment in the right-hand menu.
2. Edit the rule and type / to invoke the reference file.

Each rule can reference one asset. A reference file sharpens the accuracy of any rule that depends on it.

Set your Agent's Status

Status controls who can see and run your agent, this is the same three-state model used across every agent type in the Agent Library:

• Draft: visible only to users with the Manage Agents permission. Test your rules against a sample of assets before anyone else sees them.
• Available: visible to users with the Run Agents permission, so your wider team can run it.
• Disabled: not available for anyone to run. 

Run the Agent

1. Go to the Asset Bank or a Collection. Filter down to the assets you want checked.
2. In the bottom action menu, select Agents, then choose your agent.
3. Maximum 1,000 assets per run.

Review your Results

A run doesn't change your taxonomy on its own, unless Auto-apply is enabled (see Automate the Agent below). The agent only proposes a compliance status per asset; someone with Manage Agents permission reviews it before anything updates, and has the final say.

1. Open a completed run from the Activity screen. Each asset shows its proposed compliance status.
2. Open the report on any asset to see the rule-by-rule breakdown, which rules passed, which failed, and why.
3. If you agree with the agent, approve it. If you don't, override it with your own status, your decision always determines the asset's final compliance status, not the agent's proposal.
4. Approve assets one at a time, or select a group and approve in bulk, one action writes the compliance status across every asset you selected.
5. Only once approved does the compliance value actually land on the asset and become visible and filterable elsewhere in the DAM, search, smart collections, and so on.

Two things stay in place after your decision, so you're never trading away visibility for control:

• The original AI report doesn't disappear. Even if you override the agent's conclusion, its original report stays available on the asset's detail page, so anyone can see what the agent found versus what a human ultimately decided.
• Overrides are auditable. Any compliance decision you change gets logged in the agent's History tab, giving you a full record of proposed-versus-final status for every asset.

Put Compliance to Work in your DAM

Once the agent is writing to your taxonomy, standard Bynder mechanisms turn that value into a real gate and review queue:

• Content restrictions: the compliance metaproperty is just another taxonomy field, so you can attach permission sets to its values the same way you would for any restricted classification. An asset's visibility changes automatically as its compliance status changes.
• Smart filters: build a saved smart filter or smart collection scoped to the compliance metaproperty so reviewers can pull their queue in one click. For example, "all Partially compliant" as an in-review queue, or "all Non-compliant" as the backlog that still needs action.

Automate the Agent

• Trigger at upload: instead of running the agent manually, configure it to run automatically when new assets are uploaded, optionally scoped by metaproperty, tag, or file type. Compliance gets checked before the asset is available for wider use, not after the fact.
• Auto-apply: skip manual sign-off entirely. The agent writes its verdict straight to the mapped metaproperty the moment a run finishes. This uses the same Auto-apply Approval User you configure in the AI Control Center, so an automated run still respects your organization's permission and access rules. See AI Control Center: Global AI Instructions.

AI can make mistakes. We recommend that you only apply automated compliance evaluations after careful consideration and in consultation with the respected teams in your organization (for example, consulting with your legal counsel on topics such as regulatory compliance).

Limitations

Assets you're checking

Reference assets attached to a rule

Rules and categories

• Maximum 50 rules or 10K characters per agent, across all categories combined.
• Each rule is evaluated on its own. If a rule depends on reference information, a master color palette, approved values, include it directly in that rule rather than pointing to another rule.
• Very small or low-confidence text (under roughly 0.15% of the image area) may be skipped by text detection, rules that depend on fine print or small disclaimers may not evaluate reliably.
• Color matching runs on a downscaled copy of the image, so very fine color detail may not be captured at full precision.

Choosing How Many Agents to Set Up

• Multiple markets: if your content varies by regional regulation or standard, set up one agent per market with that market's specific rules. You can have multiple agents writing to the same metaproperty, but it’s sometimes useful to have separate compliance metaproperties for different markets, so that agents don’t overwrite each other's results, and the compliance status of each market remains clear.
• Multiple brands: if your brand portfolio has different identity elements and rules, set up one agent per brand.
• Multiple style guides: if you maintain separate guides by content type, photography, stock imagery, illustration, set up one agent per style guide.
• Multiple department reviewers: if brand, legal, compliance, marketing, product, and design all review the same content, you can use one agent and give each department its own category, as long as their rules don't conflict.

Related Articles

How To Use Bynder's AI Automation Workflows

AI Control Center: Setting up Global AI Instructions and more

Updated July 27, 2026 11:25