-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
1
-
NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.
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.
- incorporates
-
- Closed
- relates to
-
- Closed
-
- Gathering Interest
[CONFSERVER-6824] "Delete Attachment" Default Permission and Warning Needed
Björn Feustel
added a comment - This also applies to mails and comments. 
Patrick Payette
added a comment - While giving training on Confluence at University of Montreal - and in order to overcome "wiki shyness" and promote collaboration - I have to explain newcomers that they can safely leave their pages editable by others, thanks to version control and granular permissions. However there is one exception to that: restoring a page after wrongful changes won't restore deleted attachments. And the granularity of the "edit" permission does not extend to that level either. This is very much against the general principle that you "can't break anything in a wiki".
It's been 2 years since this issue was first logged - and still a strong requirement.
Patrick Payette
added a comment - While giving training on Confluence at University of Montreal - and in order to overcome "wiki shyness" and promote collaboration - I have to explain newcomers that they can safely leave their pages editable by others, thanks to version control and granular permissions. However there is one exception to that: restoring a page after wrongful changes won't restore deleted attachments. And the granularity of the "edit" permission does not extend to that level either. This is very much against the general principle that you "can't break anything in a wiki".
It's been 2 years since this issue was first logged - and still a strong requirement. 
Upvoted, Need to be able to restore attachments from Trash. Without this untrained or careless users can crush others hopes and dreams for a wiki that has a safety net. Like mine.
The warning message that pops up when you click the Delete option says that this can't be undone except by a Space Administrator. This is misleading since a Space Administrator can't undo it unless the version you want is on a backup. Not good.