An employee accidentally wrote highly confidential information into a document.
They’ve since removed it, but it still appears in history.
This is a huge security vulnerability for us. What can I do about it?
It is not possible to remove specific parts of the history of a document.
I would suggest creating a new document, copying over the current content, and then deleting the original.
(of course, this wouldn’t stop someone with the right access level from restoring the document from the trash at some point in the future 
)
I was trying to test what would happen if you first moved the document (assuming you’re referring to a Fibery Document and a rich text field) to a space that only admins had access to, then deleted it.
But I actually see that if I as an admin delete a document, the non-admins don’t see it in the trash at all.
Is this the desired behaviour?
What’s the right access level for seeing items in the trash? Does it depend on the space they are in?
This is actually a huge oversight, in my opinion
What if an employee (user) entered credit card information into a rich text field on an entity with many relationships and a long history? Removing the entity and copying everything across, re-linking relationships… it’s just not feasible
You can see how this would open up a business to huge vulnerabilities
1 Like
It would be extremely useful for an admin to be able to permanently delete a specific history entry.
Even turning off history for specific entities, documents, or databases. Sometimes it’s just not required to track changes
Even if we implement it, it will be a part of at least Pro offering (or maybe even Enterprise). I hope eventually it will be done
1 Like
I agree this is an enterprise tier offering.
The primary responsibility of tech literacy and best practices is on people. Collaborative workspaces require some degree of training.