How to prevent concurrent update attachments

In our team we've already had several times an attachment updated by person A and updated by person B, where the updates form person A were disapeared. It seems that A and B can open the same attachment and save the document where only the updates by the person who saved the attachment last remain.

What does Confluence offer to prevent this?

1 answer

1 vote

Natively, nothing, and technically, it can't anyway.

It doesn't "know" that more than one person is editing a file on another machine.  There are some add-ons in the marketplace that implement locking, so you can flag an attachment as under edit by another user and prevent people using them, but there is no way to prevent two users downloading a document and working concurrently.  Even the best locking system can't stop it happening, just warn people that someone else might be working on it.

In document and code source management there is the concept of check in and check out that could be implemented. And if you don't download the document, but edit it in the server, the system should be able to notice there are two or more people in this situation. I wouldn't say there is no way to prevent that. Simply that it's not natively implemented. 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Feb 06, 2019 in Confluence

Try out the new editing experience

Hi team, I’m Avinoam, a product manager on Confluence Cloud, and today I’m really excited to let the Community know that all customers can now try out the new editing experience and see some of the ...

792 views 33 5
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you