I too agree that as a document collaboration / management / organisation tool that it really should support archiving at a document level.

Basic functionality could be as simple as:

• Ability to set a page to be archived
  • Recording the parent node
  • Move the page to a flat archived bucket that is
    • not discover-able from within the WYSIWYG editors (web links / recently viewed pages etc)
    • can't be directly referenced in live document
• Ability to revert an archive automatically if the parent node still exists
• Ability to revert an archive manually as a fall back

Using the cloud based service and being unable to even purchase a plugin is a real kicker, having to manage it manually with a growing base of documents is... tedious. 

This would be most helpful - since we do not want to delete information but need a way to hide it if it is no longer relevant.  

Having the ability to archive a page, with impact similar to archiving a space, would very very helpful in keeping the wiki contents relevant without losing historical reference information. It would be possible to create an archived space, and move the desired page to the archived space, but with this solution you lose the original context for the page (what space did it belong to, where did it fit in the page hierarchy, what was its parent, etc. etc.). So, being able to archive an individual page, without having to move it or remove it from its natural home within the wiki structure, would be an extremely valuable feature.

So this is feature for which we need to pay?

Sorry but that is shocking...this is a document management system; surely archiving should be come as an included feature?

Hi Amel!

What you described can be fully automated using the Archiving Plugin for Confluence.

It will:

• automatically report you the pages that should be archived
• automatically move those pages to hidden archive spaces, based on your configuration

Learn more or try it free