Check your content against compliance rules before submitting for approval.
Know exactly what needs to be fixed and save your approver's time.
Starting a Scan
Double-click any file in your library to open it in the File Viewer.
Click Scan in the right-hand toolbar.
Review the scan settings:
Setting | What it does |
Scan Context | Filled in automatically from the file's details: channel, products, audience, and geography. If the file belongs to a project with an audience already set, the audience fills in automatically. To change the context, update the file's details. |
Preset | Under Customize Results, pick a saved scan preset. Your admin may lock the preset or limit which presets you can use. |
Regulators | Federal, state and country regulations. State regulations are picked up from the file's geography. |
Company Policies, Disclosures, Trademarks, Brand Guidelines | Which internal rules to check: your own policies, required disclosure copy, marks and their first use, and tone, voice and visual rules. |
Brand Portal Libraries | Check against approved rates, offers, studies, and marks. You can leave individual libraries out of a scan. |
Each check under What to check (inside Customize Results) is a switch and is on by default. At least one must be on to run a scan.
Click Run Compliance Scan.
Understanding Scan Results
Each scan gives the file a compliance score out of 100. Under the score, click the Checked: line, which counts what was checked in each category, to expand the full list of every regulation, disclosure, and custom policy the scan checked, not just a count. This is a good way to confirm a regulation that should apply was actually included.
Findings are grouped by regulator or policy source, and each one is tagged with a risk level:
Flag | What it means |
đ´ High | Fix this before publishing, could mean fines or regulatory action. |
đĄ Medium | Should review, could attract scrutiny. |
đľ Low | Minor issue, nice to fix but not critical. |
Click any flag to see the exact text that's problematic, where it appears in the asset, and which policy rule it violates.
Fix the issues, upload a new version, and scan again to confirm they're resolved.
To dismiss findings or give relevancy feedback on them, see Working with Scan Findings.