Forum Discussion
Storyline 360 Collaboration Possibility?
- 2 years ago
Hi, everyone!
I have some great news to share!
We’ve just released an update for Review 360 which includes cool new features:
New: Create shared team folders in Review 360 to organize your content, assign permissions, and invite collaborators. You can even allow multiple authors to publish new versions of a course to the same Review 360 project.
And because Review 360 is a web app, there's nothing to install! New features and fixes are available immediately.
Please let us know if you have any questions by reaching out to our Support Engineers directly.
Have a great day!
Maybe utilise Review 360? Would be good if we can have the option to 'publish for development' the work from Storyline to Review 360 and attached the .story file, so team members can review and make changes to the file and in turn also attached their .story version to the same review and allow the original project owner to see what version correspond to which .story file? At the end of the project, we can close the review and have the final .story... and all of this happens from within storyline.
That sounds complicated. We use Review 360 when we have completed enough of our project or a piece of our project that is ready for review by our stakeholders. However, while we're in the development stage we utilize one story file on a shared drive that allows us to work on the story as a team. We can certainly breakout the story into scenes and assign scenes to different people but they are not separate stories that need to be merged later. Just one working file. Keeps it simple.
- AndreasKuswara-5 years agoCommunity Member
Yes, that would depend on the circumstances, in one of our projects, the project itself is massive. I think (from memory) amount to 100 slides. We can't break it apart, and teamwork on this project was a nightmare. Maybe we can improve on the design, I don't know, I wasn't the one design, but our team was assigned to update it with limited time.
Other projects, we collaborate on the design, or one designer stuck and asked another to review and make changes. Since we all work from home, we are using Teamviewer at the moment, but it is so so slow. So we have to copy it to local, work on it, once I completed my version, I copy it to the network drive again, then the same happens on the other side. I just thought it might be an even better way if when publishing we can tick a box to say publish .story along with it, so on the other side, another designer can 'download' the story rather than working with many versions of the file.
But I agree with you to try to keep things as simple as possible that works with the circumstances you are facing.