Different Reviewers by Document on the Same Task

It would be nice to be able to specify different reviewers for multiple documents within the same task. Right now, whoever is assigned as a reviewer is assigned to all documents marked for review.

Hochstimmen 8
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
3 Kommentare

Yes, this could be useful if you want to ask assignees to review docs as part of onboarding, for example.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

I will add my support to this request too! Right now I have a group of 6 files on a task: One person needs review access to every file, two people need review access for different halfs of the files, and then each of 6 files needs one additional person to only their respective file.

The only way I can see to do this right now is create 6 different tasks and 6 reviews with 3 people on each (the one who needs to see them all, the one who needs to see this half, and the one person who needs to see only one particular file). Thus sending out 6 different review invitation emails to the most senior leadership stakeholder, and 3 to the nest most senior people, which IMO is not a good look and likely to confuse or annoy.

Or add all 9 people to one review where everyone can see everything, and hope they stay in their own lanes...

If I could just be sending the leaders one invitation with all of their respective links, and then sending the other 6 individuals one invitation with only their document link it would be so much better of an experience for them and make us look more organized.

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos
Avatar
Juan

Thank you for adding your support for this suggestion and for sharing your use cases with us! 👍

0
👍 Spot On 💡 Innovative Approach 💪 Stellar Advice ✅ Solved 🪄 Remove Kudos

Folllowing List for Post: Different Reviewers by Document on the Same Task
[this list is visible for admins and agents only]

Oben

Bevorstehende Live-Sitzungen