There isn't a way for multiple authors to work on a single Storyline 360 project file. You can however use the Shared Team Slides feature to quickly share slides and entire projects with team members, allowing them to work on the same content you are working on.
Working on a .story file over a network can corrupt the file. Thus, a .story file should always be on a local hard drive when it's being edited.
When two or more people need to edit a given project, they'll have to take turns editing. For example, developer A might create the file on their local drive. When the file is ready, they could upload a copy to a shared network drive. Develop B would download the file to their local drive, edit it as needed, and then upload a copy of that to the shared network drive.
Obviously, the developers need to clearly communicate when each will be editing. There should also be a good naming convention that indicates progressive versions. And it's a good idea to keep all versions until the project is finalized.
2 Replies
Hi Claire,
Thanks for reaching out!
There isn't a way for multiple authors to work on a single Storyline 360 project file. You can however use the Shared Team Slides feature to quickly share slides and entire projects with team members, allowing them to work on the same content you are working on.
Hope this helps!
Working on a .story file over a network can corrupt the file. Thus, a .story file should always be on a local hard drive when it's being edited.
When two or more people need to edit a given project, they'll have to take turns editing. For example, developer A might create the file on their local drive. When the file is ready, they could upload a copy to a shared network drive. Develop B would download the file to their local drive, edit it as needed, and then upload a copy of that to the shared network drive.
Obviously, the developers need to clearly communicate when each will be editing. There should also be a good naming convention that indicates progressive versions. And it's a good idea to keep all versions until the project is finalized.