Define how content moves through review before it can be used.
No more email chains or lost approvals. Everything is tracked in one place.
How to Get There
Click Settings in the left sidebar.
Under Company, select the Approvals section.
What Needs Approval
Two switches control what needs review. Require Approval for Disclosures & Products: when off, disclosures and products are auto-approved on creation or submission. Require Approval for Assets: when on, team members must submit assets for approval before they can be published.
With asset approval on, choose the Approval trigger criteria. Assets that don't match the criteria are auto-approved:
Setting | What happens | Best for |
All Assets (Manual) | Every asset goes through manual review, regardless of risk flags | Strict compliance (FINRA, etc.) |
Any Risk Flag | Any asset with an identified risk needs review | Balanced approach |
High & Medium Risk Flags | Assets with only low-risk flags auto-approve | Faster workflows |
High Risk Flags Only | Only assets with high-risk issues need review | High-velocity teams |
Auto-approve above a score | Assets auto-approve when the score clears the Minimum score to auto-approve you set (0 to 100); everything else needs review | Teams that rely on scan scores |
⚠️ For FINRA-regulated companies: We recommend requiring review for all assets since a licensed principal must review marketing materials.
Require a scan before submission: turn on Require completed scan before submit to block submission until a scan has completed on the current version of the asset, so reviewers always receive it with findings ready.
Creating an Approval Flow
Approval Flows → Add Flow.
Enter a Flow Name (e.g., 'Marketing Review' or 'Legal Approval').
Add a description so your team knows when to use it.
Set the flow's Status: Draft (the default, so you can build and review it before anyone can route work through it), Active (live now) or Inactive. Draft and inactive flows don't appear in the "Submit for Approval" picker.
Turn on Applies to Reach (Social) if this flow should also appear in the "Submit for Approval" picker for social posts.
Optionally, set a Minimum scan score to submit (0 to 100). Assets scoring below it can't be submitted to this flow. Leave it blank for no minimum.
Add your first stage:
Give it a Stage Name (e.g., 'Legal')
Add the Approvers: people, groups, or both. For each group you add, a Group quorum setting appears: Any member (the default, one member approves for the group) or All members (every member of the group must approve). All members only takes effect when the stage's Requirement is Everyone (AND).
Set the Requirement: Any One (OR) (the stage completes when one approver approves) or Everyone (AND) (all approvers must approve)
Add more stages if needed with Add Stage. Above each stage after the first, choose how it runs:
Runs after previous stage (the default): the stage opens only once the stage before it is complete.
Runs together with previous stage: the stage opens at the same time as the stage before it, so both are reviewed at once. A later stage set to run after them waits until all of them are complete.
Click Create Flow.
In the Approval Flows list, each flow is labeled Sequential, Parallel or Mixed depending on how its stages are set to run.
You can create multiple flows for different content types: quick review for social, full review for campaigns.
Setting Expiration Rules
Approved content doesn't stay approved forever. Under Expiration Settings, set when it expires:
Turn on Enable expiration dates.
Enter the Default Expiration (days). Assets expire this many days after upload.
Choose a Default expiration approval flow. When a file expires, this flow is triggered automatically for re-approval. Choose No Re-approval Required to skip it.
Never worry about outdated content staying live. Warrant tracks it for you.