Forum Discussion
Review 360: Publish to Team Space
Hi there. We're predominantly using the Team space for our Rise courses since we collaborate on all our material. We're a small team, so we all help with editing and implementing feedback.
My issue is that when a course that exists in the Rise Team space is published to Review, it automatically publishes to a Private Review space. I've scoured permissions and default options, but I can't find a way for courses to be published directly to the Team space in Review. They have to be manually moved.
Is there a way to choose where the course gets published? We work in different time zones, so if one person is not online and someone else needs to implement feedback, it can be challenging if the Review lives in a Private space.
I would have thought that something that lives in the Team space in Rise would automatically go to the Team space in Review, since it was already set as a Team item?
Looking forward to your suggestions on this!
1 Reply
Hello MKitshoff,
Thanks for explaining your workflow. I can absolutely understand how this creates friction, especially when your team is collaborating across time zones.
When you publish from Rise 360 to Review 360, the item will always publish to your Private directory first. There isn’t currently a setting that allows you to choose a Team folder as the default publish destination.
Once the item is moved into a Team folder and collaborators are given editor access to that folder, other team members can publish new versions of that item directly, even if the original publisher isn’t online. Folder permissions in Review control who can publish new versions, while collaborator roles in Rise control who can publish the course initially.
I understand why you’d expect a course that lives in a Rise Team folder to automatically publish into a Team space in Review. That would certainly make collaborative publishing smoother.
If you’d like to see changes to how publishing destinations are handled, feel free to share a bit more about what an ideal workflow would look like for your team. We’re happy to gather that feedback and pass it along to our product team.
