Review incoming assets. Keep decisions with the file.
Unapproved assets are visible only to administrators. Approve content when it is ready, and use permissions to decide who can access the approved material.
Give content review a clear place.
Choose which uploads need review.
Require approval for all uploads to a collection or for uploads from selected contributors. Only administrators can see an asset until it is approved.
Check the file and approve it.
Administrators can find the files waiting for approval, review them and record a decision.
The latest status, reviewer, date and comment stay with the asset. Permissions determine who can access it once it is approved.
Keep feedback close to the material.
When feedback is enabled, people can leave a message with the asset. Managers can review the feedback and respond by email.
A few useful answers.
What is required to use asset approvals?
Asset approvals must be enabled for the account. Reviewers need management access, and upload rules are set on the collections receiving the files.
Does approval establish legal permission to use a file?
Approval records a content decision. The asset’s license and usage restrictions describe how it may be used, while access settings determine who can reach it.
What review information is kept with the asset?
The asset shows its latest approval status, reviewer, decision date and comment. This gives the next person useful context when they return to the file.
Give incoming content a clear review path.
Explore the upload rules, decisions and access settings that fit your team’s content process.