Forum Discussion
Storyline 360 Collaboration Possibility?
Hello I'm wondering if there is a way to collaborate on Storyline 360 projects- like our team has in the past with an owner and a couple of collaborators in Rise.
Attached are two photos, they are the closest pieces of information I found that are what I am looking for.
We tried using team slides today, and it appeared to be an issue, as it seems we were both in one of the projects at the same time, and when this would happen before in Rise you could see that someone else was in a certain Lesson because Rise would let you know.
Could team slides be used like this for us in the future, but we would have to coordinate on who was working on which projects at what time? Or will it always make us save the project as a new project? Essentially duplicating the project each time it is opened by someone else and edits are made?
I am looking for a good way to collaborate on our projects in Storyline 360 where we can all make edits- and not have to worry that we are making edits or changes to an 'older version' of our training modules.
Hope this makes sense! Any help would be great! Thank you!
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!
43 Replies
I second the need for Team collaboration in Storyline 360. Sharing slides, scenes and projects is not really collaboration as once you share those options, the team no longer has any visibility in real time as to what is going on. What is desirable is to allow different team members work on a scene, or slide in the same project as the others.
We've actually figured out a great work around so that we can collaborate on Storyline. We use MS Teams and SharePoint in our day to day work. So when one of us creates a Storyline project we save it to our MS Team channel under "Files". We cannot open the file directly from the channel, but can open it from the Storyline app by pointing to the folder where the story is saved. Since my teammate is in Poland and I am in the US, we can both access the same file and simply save our changes at the end of our shifts. No publishing or sharing required. I would think that anyone who has a shared drive where their team members can all access files should be able to utilize the same process and therefore work on the same story. I'm not sure you could have multiple people working simultaneously in the same file without saving in between changes, but you can at least work without the added steps of sharing/publishing between changes.
I'm curious if you've never experienced problems using this process? I'd like to consider this but hadn't because of all the dire warnings I've seen about working from a cloud or network drive. Never understood why the claimed latency issues would affect these files any differently that other desktop apps.
I haven't experienced any problems other than the typical problems in dealing with cloud files. Utilizing the story on a shared drive/Teams has been a life saver for us. So far so good.
how would you open a MS Teams file directly from the storyline?
In MSTeams under Files you may either use the Sync option to create a link to your hard drive or Open in SharePoint and select the option to Add Shortcut to OneDrive. Open Storyline and select (at the bottom) "Browse for more..." Now that you have the file accessible from your File Explorer window, you can locate the story file and Storyline will open it. Once you've opened the file in Storyline it will appear under "Recent" the next time you open Storyline, so you don't have to browse for it each time. I hope this is helpful.
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.
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.
I believe that having a real collaboration on Storyline 360 is a key point and the solution to share slides is not really something that is helping developers in working all together at the same project. I add my voice to have a real collaboration feature on storyline 360.
Agreed! Adding my voice to the request for enhanced Teams collaboration features!
I agree. Our team is currently experiencing the same struggles mentioned already. We are in the same office, and we have shared the file on a flash drive or via MS Teams. To add to the difficulty, it seems like each time the next person opens the file, things that person doesn't even touch become broken. Quiz scoring, photos nudged off center, it really just goes on and on. We are working well together, but the tool itself is frustrating us.
II agree with all of the aforementioned issues regarding collaboration and add the following:
I would love to be able to publish a project to 360 review and have it appear on my team members' dashboard in 360 Review. Is there a way to do this and I've just missed it?
I'm new to Articulate's teams environment, so I'm hoping I've just missed how to do this.Would indeed be very good to have a proper teamworking solution in Storyline. Teamslides are just not enough for cooperating in titles. +1 for that.
Hi there!
Just want to add my 2Cents and echoing many others I think the Team Slides makes sense for having a central repository for your shared content but I think it would be great to be able to work in real-time on a Storyline Project similar to working in PowerPoint where you can work on a file as a group. Please bring Storyline to the Cloud :)Adding my vote to this thread! Honestly, investing programmatically in developing a SaaS solution for real-time, collaborative Storyline authoring would be a strategic competitive advantage for Articulate.
I just look to all the really incredible online tools like photo editing, infographics, docs, etc. where my team can work on things simultaneously and wonder why this can't be done for instructional design/development.
All the workarounds (at the team level) add time, cost, grief, and risk to each project. Articulate — if you build the solution, you have a whole community of companies and people who will buy it.
