Coauthoring in Word is not blocking the paragraph

%3CLINGO-SUB%20id%3D%22lingo-sub-1044499%22%20slang%3D%22en-US%22%3ECoauthoring%20in%20Word%20is%20not%20blocking%20the%20paragraph%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1044499%22%20slang%3D%22en-US%22%3E%3CP%3EOne%20group%20in%20our%20company%20is%20composed%20of%20enthusiastic%20users%20of%20the%20coauthoring%20with%20SharePoint%202013%20and%20Word%202013.%3C%2FP%3E%3CP%3EThey%20were%20recently%20migrated%20to%20Word%20Online%20and%20we%20cannot%20recreate%20their%20favorite%20ways%20for%20coauthoring%20when%20we%20decided%20to%20use%20SharePoint%20Online.%3C%2FP%3E%3CP%3E1)%20We%20leave%20the%20automatic%20save%20on%20and%20open%20the%20files%20in%20the%20application.%20As%20a%20result%2C%20they%20can%20see%20real-time%20collaboration%20(even%20in%20the%20same%20paragraph)%20but%3A%3C%2FP%3E%3CUL%3E%3CLI%3EThey%20have%20too%20many%20versions%20in%20the%20history.%20It%20becomes%20too%20hard%20to%20find%20a%20version%20they%20would%20want%20to%20restore.%3C%2FLI%3E%3CLI%3EThey%20cannot%20see%20the%20last%20updates%20in%20green%20highlight.%20They%20don%E2%80%99t%20know%20if%20somebody%20made%20immediate%20changes%20on%20page%201%20while%20they%20are%20working%20on%20page%205.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E2)%20We%20disactivate%20the%20automatic%20save%20and%20open%20the%20files%20in%20the%20application.%20They%20must%20save%20each%20time%20they%20make%20important%20changes.%3C%2FP%3E%3CUL%3E%3CLI%3EThe%20behaviour%20is%20like%20before%3A%20the%20version%20history%20is%20reasonable%2C%20and%20they%20see%20the%20green%20highlighted%20text%20when%20updates%20arrive.%3C%2FLI%3E%3CLI%3EBut%20a%20paragraph%20is%20not%20blocked%20for%20editing%20when%20somebody%20is%20changing%20it.%20Users%20cannot%20see%20when%20somebody%20else%20is%20changing%20the%20paragraph.%20It%20causes%20conflicts.%3C%2FLI%3E%3C%2FUL%3E%3CP%3ENeither%20option%20is%20optimal.%20Do%20you%20get%20the%20same%20behaviours%3F%20Do%20you%20have%20other%20ideas%20on%20how%20to%20accommodate%20our%20users%3F%20Do%20you%20know%20if%20coauthoring%20is%20going%20to%20change%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1044499%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Contributor

One group in our company is composed of enthusiastic users of the coauthoring with SharePoint 2013 and Word 2013.

They were recently migrated to Word Online and we cannot recreate their favorite ways for coauthoring when we decided to use SharePoint Online.

1) We leave the automatic save on and open the files in the application. As a result, they can see real-time collaboration (even in the same paragraph) but:

  • They have too many versions in the history. It becomes too hard to find a version they would want to restore.
  • They cannot see the last updates in green highlight. They don’t know if somebody made immediate changes on page 1 while they are working on page 5.

2) We disactivate the automatic save and open the files in the application. They must save each time they make important changes.

  • The behaviour is like before: the version history is reasonable, and they see the green highlighted text when updates arrive.
  • But a paragraph is not blocked for editing when somebody is changing it. Users cannot see when somebody else is changing the paragraph. It causes conflicts.

Neither option is optimal. Do you get the same behaviours? Do you have other ideas on how to accommodate our users? Do you know if coauthoring is going to change?

0 Replies