Approvals
Make sure every asset gets reviewed before it goes live. No more 'oops, wrong image' moments.
The review workflow
Every asset in a workspace with approvals enabled follows a simple lifecycle:
Assets can also be Rejected, which sends them back to the creator for changes. After fixing the issues, the creator resubmits and the asset goes back to Pending Review.
What each status means
Draft
The asset is being prepared and is not ready for review yet. Access follows workspace roles and any resource-specific permissions. Make the required edits before submitting it.
Pending Review
The creator has submitted the asset for review. It shows up in the review queue for people who can access the item and have approval permission. Review the current file and any validation warnings before deciding.
Approved
A reviewer has signed off on the asset. It is ready to be published. You can publish immediately or wait and publish a batch together.
Rejected
The reviewer found issues and recorded a rejection reason. The asset remains Rejected until it is corrected and submitted for review again.
Published
Approval and delivery are separate. Check the chosen destination’s publish or delivery status before treating an approved asset as live. A connected account alone does not confirm delivery.
How items reach Review
Supplier uploads and AI results that need sign-off go to Review on their own. You do not submit them by hand.
Who can approve?
By default, Owners, Admins and Reviewers can approve or reject assets. You can also grant approval permission to specific Editors from Settings > Team. This is useful when a senior designer needs to review work without having full Admin access.
Viewers, Uploaders, and Suppliers do not have approval permission by default. If your team requires independent sign-off, assign a different reviewer.