Critical information loss can occur too easily with attachments. As opposed to wiki pages (which are versioned and recoverable in case of deletion) important attachments can be lost by deletion when not protected by a restriction at the page level. Moreover, they cannot be recovered from the trash can.

Our company needs to trust Confluence with critical information in the form of attachments. Our users must be able to leave a page unrestricted while relying on Confluence that their attachments will not be deleted by mistake or by the action of another single user without any chance of recovering it.

Confluence needs a special restriction/control over attachments. Currently, it leaves important documentation unprotected/unrecoverable in case of accidental deletion.

The solution should include a default permission for deletion; a warning message when righfully deleting an attachment; and the ability to recover it from the trash can.