I'm wondering if there is a way to allow a stakeholder to comment privately, they do not want their comment to be posted where other stakeholders can see it.
Thank you for your reply! I thin Review 360 is very helpful for a variety
of reasons. I think that in diverse stakeholder groups there may be groups
that feel marginalized, and thus may wish to put send their comment
directly to the editor, rather than have their topic be a part of the
dialogue.
Thanks for taking the time to share why private comments are beneficial! I’ll be happy to pass your thoughts on to our product team, but you can also feel free to detail them through a feature request!
This may also be handy when working with a test group. This is what I'm working with right now. Where I want the SME's to see each others comments and discuss with each other, I want test users to only see their own comments and not be influenced by each other. I'm solving this by sending the test user each their own link. It would be great if I could disable commenters seeing each others comments, but still see everything in one place myself. I think I can be identified by the system as the developer?
Thank you for sharing this with us! I've created a feature request on your behalf so that we can continue tracking this request. I've also linked this discussion to the report so that we can return with an update!
We've got the same issue as Susanne. I work for a government contractor and we do our own internal reviews in an INTERNAL link, but then create a new review link called EXTERNAL for the client review. We don't want the client seeing our internal comments. However, then the ISDs need to make changes to the courseware based on the client review and send that to the programmer/GA. After the programmer makes the changes, the ISD then reviews it in the INTERNAL link to verify changes are made, and then for the final client review it is published in the EXTERNAL link. It would be great to disable our internal comments for the client and then just have one link that is controlled by the internal team. Do you think this is something that can get rolled out in 2021?
Thank you for sharing your workflow and how you would like to use this feature. I've added this information to our report.
I wanted to share some information about how we manage these feature requests as that may be helpful. You can find the items that are currently on our roadmap here.
I also have use for this feature. I am responsible for reviewing all content created by my L&D department and providing comments, however, in some cases i don't want our internal comments/conversations viewable by the other stakeholders/clients to protect the developers relationship with the stakeholders/clients.
While this feature hasn't made it to our feature roadmap yet, this discussion is connected to the report, so we'll be sure to notify you when we have news to share.
10 Replies
Hi Axcelle,
Review 360 was designed to gather all your feedback in one place for easy review and get everyone on the same page.
At the moment, we do not have a feature for private commenting, but I'd love to hear more about why you'd like this feature!
Hi Ren,
Thank you for your reply! I thin Review 360 is very helpful for a variety
of reasons. I think that in diverse stakeholder groups there may be groups
that feel marginalized, and thus may wish to put send their comment
directly to the editor, rather than have their topic be a part of the
dialogue.
Thank you,
Axcelle
Hi Axcelle,
Thanks for taking the time to share why private comments are beneficial! I’ll be happy to pass your thoughts on to our product team, but you can also feel free to detail them through a feature request!
This may also be handy when working with a test group. This is what I'm working with right now. Where I want the SME's to see each others comments and discuss with each other, I want test users to only see their own comments and not be influenced by each other. I'm solving this by sending the test user each their own link. It would be great if I could disable commenters seeing each others comments, but still see everything in one place myself. I think I can be identified by the system as the developer?
Hi Susanne!
Thank you for sharing this with us! I've created a feature request on your behalf so that we can continue tracking this request. I've also linked this discussion to the report so that we can return with an update!
Lauren,
We've got the same issue as Susanne. I work for a government contractor and we do our own internal reviews in an INTERNAL link, but then create a new review link called EXTERNAL for the client review. We don't want the client seeing our internal comments. However, then the ISDs need to make changes to the courseware based on the client review and send that to the programmer/GA. After the programmer makes the changes, the ISD then reviews it in the INTERNAL link to verify changes are made, and then for the final client review it is published in the EXTERNAL link. It would be great to disable our internal comments for the client and then just have one link that is controlled by the internal team. Do you think this is something that can get rolled out in 2021?
Hi Ellen,
Thank you for sharing your workflow and how you would like to use this feature. I've added this information to our report.
I wanted to share some information about how we manage these feature requests as that may be helpful. You can find the items that are currently on our roadmap here.
I also have use for this feature. I am responsible for reviewing all content created by my L&D department and providing comments, however, in some cases i don't want our internal comments/conversations viewable by the other stakeholders/clients to protect the developers relationship with the stakeholders/clients.
Hi, I have exactly the same query. Did anything happen with this request?
Hi, Steven,
While this feature hasn't made it to our feature roadmap yet, this discussion is connected to the report, so we'll be sure to notify you when we have news to share.