Co-authoring documents

This page applies to: New Document Editor. Switching between the new and old editor is only possible temporarily as we finish rolling out the new editor. 

IT Glue co-authoring functionality helps make it easier for your team to work together to publish new content. When you want to work on a document, you open it as usual. If someone has already made changes but hasn't yet published them, you will see the changes that have already been made.

If you edit a document that is still being edited, IT Glue will display a message informing you that you are editing an outdated page and giving you the option to load the more up-to-date version or resume editing your current draft.

Let’s look at how this works.

I open a document I need to update and start editing it.

By default, IT Glue checks for conflicts once every 60 seconds or when certain predefined events occur, for example, publishing the document or adding new content blocks.

After about a minute of typing into an existing content block, I get an alert and see that my colleague has already started editing the same document:

resume_editing.png

I can't continue editing until I choose one of the the two options: load newer or resume editing.

In this case, I know my colleague was adding some technical specifications from an email we both received but he is just heading into a meeting. I am trying to meet a deadline, so I click on the load newer link to complete the changes.

Here's what my colleague sees after he comes out of his meeting and starts to edit the same document:

resume_editing_reverse.png

If he came back and tried to publish his changes without making any new edits, here is what he would see instead:

continue_publishing.png

If both of us publish different versions of the document, the two versions will be recorded in the revision history, and whichever one was published last will be the live version. Versioning makes it possible to roll back edits and determine who published a specific draft.

Was this article helpful?
0 out of 0 found this helpful