SpiderOak CrossClave allows for teams to share files between each other. Sometimes when team members are both working on the same file at the same time they can encounter bumps that can cause frustration. For example:
Let's say you had an important spreadsheet that multiple members of your team accessed daily to add information to or pull information from. One team member opens the spreadsheet and starts working, adding new text or fields. Another team member logs on, and also opens the file and begins work. The file both of them have opened is the same file. The second team member is working on adding information to the spreadsheet that the first team member won't see, and vice versa. This creates a problem as it will mean a lot of wasted effort for one of the users and can also cause confusion as CrossClave will save the files as historical versions depending on which was pushed to CrossClave most recently.
In order to prevent this wasted effort and avoid the potential of file conflicts we recommend working in the following manner.
1. Open the file you intend to work on from *within* the CrossClave application.
2. Proceed to work on your file. We recommend working in 15-30 minute increments.
3. Save the file you are working on in whatever manner it requires.
4. Close the file.
5. Focus the CrossClave application.
6. Navigate to the file within CrossClave and choose 'Commit'.
7. If desired, re-open the file from within CrossClave.
To re-iterate, whenever working in CrossClave this is the best way to work within the application. Simply saving from within the application does not create a new historical version. You must perform the steps listed above to create a new version of the file, if you do not save in the application, close the application, navigate to CrossClave and commit the newly saved version then there will not be a new historical version created and anyone else accessing the file will get an old version. Also remember, you must open the file from within CrossClave if you want to create a new version within CrossClave.
Article is closed for comments.