How do you maintain historical pages/versions?

[Justin Wong]

Hi community,

We have a question on how you maintain historical confluence versions/pages.

We have a tighter governance  around them and thus like to understand best practices.  For example, the audit team can inspect a page and its artefacts dated 6 months ago.

 Another point is around space admins and permissions.  While we should trust admins on permissioning, we have hundreds of teams/admins and prefer to err on the side of caution on permission assignments and accidental deletions.

 It’s down to 2 options using 1. page versions/history or 2. creating new (copy) pages separating them from historical ones.

1. Using versions/Page IDs.  This is easiest.  However versioned pages when deleted is a silent operation and they do not appear in trash (goes away completely).
2. Create a copy page (new URL) separating the old one and this could be done often.  In the event of a page delete, it goes into the trash and can be restored as a safeguard.   However it requires additional housekeeping and inconvenience to teams.

 What do you do today and recommendations?  Thanks.

[Deleted user]

Hi @Justin Wong,

Regarding your first question about archiving pages for later auditing – I think that the Scroll Documents app for Confluence might be useful for that use case.

With Scroll Documents, you can save versions of trees of Confluence pages. When you save a version, you essentially snapshot the page structure and content of the saved pages at the current time.

When saving the version, you also assign the version a name and a change comment, so versions are easily findable later on. The permissions on the pages you version also apply to the saved version pages.

If you think that Scroll Documents might be interesting for your use case, you can find out more at https://www.k15t.com/software/scroll-documents, and I'll also be happy to answer any questions you have.

Cheers, Tom.