Make your first review decisions
In this tutorial, we’re going to make the final decision on a review’s assets as its decision maker, then check an amended version against the one we rejected. Decision makers are the people whose approval lets content go on to be published, so knowing what changed between versions matters. By the end, you’ll have approved one asset, rejected another, and approved its amended version after comparing the two.
This is part 2 of 3 in the reviewer tutorials. Previous: Give feedback in your first review. Next: Give feedback on your first video.
Prerequisites
To follow this tutorial, you need:
-
An invitation to an active review with at least two assets, in which you’re the decision maker. Ask a colleague to create the review and give you the Decision Maker role. If your colleague is working through Review and publish your first adaptations, the review they create there is set up for this tutorial.
-
The same colleague, ready to amend the asset you reject in step 2, so that a new version reaches you in step 3.
If you have a Storyteq CMP account, a user role with at least the Reviewer role for Reviews, under Adaptation Studio, also lists the review on your Reviews page. Each role’s permissions are listed in User role presets and permissions.
It helps to have done Give feedback in your first review first, because this tutorial also works in Review Studio.
What we’ll create
We’ll approve one asset in the review and reject the other with a comment saying why. When our colleague sends the amended version, we’ll open it, compare it with the rejected version, and approve it.
Between steps 2 and 3, you wait for your colleague to amend the rejected asset. Apart from that wait, the tutorial takes about 15 minutes, including the videos, in three steps:
Step 1: Leave a reason
A rejection is only useful if the person amending the asset knows what to change. So before deciding, we’ll leave the reason on the asset itself.
This step’s video also covers step 2.
-
Open the review from its invitation email, as in step 1 of Give feedback in your first review.
-
Select the second asset in the review.
-
Add an annotation or a general comment saying what needs to change. For example,
Please change the headline to Summer has arrived. -
Post the comment.
You’ll notice that the comment appears in the comments panel, as it did when you gave feedback as a reviewer. Decision makers have the same feedback tools as reviewers, plus the decision.
Step 2: Approve and submit your decisions
Now we’ll record a decision on each asset. The tile view puts every asset side by side, which makes deciding on several quicker.
-
Switch to the tile grid view.
-
Select the first asset, then select the tick to approve it, and confirm.
-
Select the second asset, then select the cross to reject it, and confirm.
You’ll notice that:
-
Each asset now shows its decision: approved or rejected.
-
The review is no longer open for feedback.
When the decision maker has decided on every asset, the review finishes. The review’s owner receives an email with the outcome for each asset, and can read your comment on the rejected one.
Your colleague now amends the rejected asset. Wait for the next email before carrying on.
Step 3: Compare the new version
When the amended asset is ready, you receive a new email inviting you to review it.
-
Open the new email.
You’ll notice that it includes the asset’s version number, so it’s clear which version you’re reviewing.
-
Select Go to Review.
Now we’ll check our comment was acted on.
-
Use the version dropdown at the top of the review to switch between the new version and the one you rejected.
-
Select Compare.
The window splits in two: the latest version on the left, the previous version on the right, with your earlier comment beside it.
-
Turn on Auto Compare.
Changes between the versions are highlighted in red.
-
Switch to the Overlay view and move the slider left and right.
-
When you’re satisfied the headline now reads
Summer has arrived, approve the asset as in step 2.
You’ll notice that:
-
You can’t add comments to the previous version, because it was locked when you rejected it.
-
Auto Compare and Overlay highlight the change, so you don’t have to find it by eye.
The finished decisions
Here’s where the review stands:
-
First asset: approved in step 2.
-
Second asset: rejected in step 2 with a reason, then approved at version 2 in step 3.
-
Next: both assets are approved, so the review’s owner can publish them.
Conclusion
In this tutorial, you’ve learned how to:
-
Leave the reason for a rejection on the asset.
-
Approve and reject assets as a decision maker.
-
Open an amended version of an asset.
-
Compare two versions with Compare, Auto Compare, and Overlay.
Create and run a review explains how reviews are set up and run. To publish approved content, use Publish adaptations to the DAM.