Best practices for file management

I never had problems storing back-up files on a SharePoint site. But I never open a .story file unless it's on my hard drive. Also, I always close .story files before I put my PC to sleep. That's a tip I got years ago, from an early hero who said the sleep-wake process might corrupt an open file. I don't know if that'd still be the case, but it's an easy tip to follow, and it sure doesn't hurt. 

• More re: best practices for storage. In addition to the .story file, the storage process should back up other source files needed for the project. For example, be sure to back up any special images or illustrations, videos, and the editable source files for any attachments. I also recommend backing up audio transcripts and/or other script materials.
• FYI: Articulate recently added a feature that saves a copy of the .story file when you publish to Review 360. Here's more info about that: https://community.articulate.com/discussions/articulate-storyline/new-in-storyline-360-cloud-backup-beta  

When you attach a PDF or other file, it gets saved as part of the project. Thus, if you transfer the .story file to someone else, they could publish it, and the attachment would be there.

However, this also means that if you update the original file, the attachment in the .story file doesn't get updated. Instead, you have to replace it with the updated version. Thus, in addition to having a good version-control process for the .story file, you need a good version-control process for attachments.

• More FYI: Here's the User Guide info about attachments: https://community.articulate.com/series/articulate-storyline-360/articles/articulate-storyline-360-user-guide-how-to-attach-resources