Confluence keeps a history of changes for each page, that is a page version is created and a version number assigned each time a change is made to a page.

It is possible to view all versions of a page, to roll back to a previous version, or to compare two versions. See how this works in this demo video.

It is possible that two or more people work on a page at the same time concurrently. Confluence will try to merge these changes automatically if the changes do not interfere with each other. This is the case when the changes have been made at different parts of the page but there are a few pitfalls.  For example, tables are seen as one Entity on a page. If two editors work on different parts of a large table, the entire table is being saved each time one of the two hits save. This can overwrite changes even though both edits were in different parts of the table.

Our LINCHPIN Intranet solution offers all that Confluence offers plus more sophisticated revision management features which make your life a bit easier and concurrent editing safer, including concurrent editing of attached files.

By employing the Arsenale Lockpoint Attachment Checkout plugin, we added locking functionality for attachments so that collaboration becomes more controlled and safer.

Arsenale Lockpoint integrates well with other plugins and helps those in particular, who need to collaborate a lot using attached documents rather than Wiki pages.

Many Intranets are used for editorial publishing of content. Linchpin has some great features as it incorporates Comalatech Ad hoc Workflows. This allows pages to be edited by a group of people in a workflow before it becomes "published" to the rest of the users.

This publishing can be don between different spaces, for example, in an Extranet situation where it is important to have some quality assurance process implemented before making content publicly available. Read our knowledge base article on Workflows in LINCHPIN.