Most of the time we have corrected this using workflow. There are two main ways that we do this:

1) When a user adds a document, it goes into a "working" area that allows someone to see through redaction and make any needed redaction. At this time the user also adds/changes initial metadata so that it is routed further along in the process. Whatever folder your workflow routes it to at that point will not have the see through redaction right. The main drawback with this is that the end user cannot add additional redaction at these later steps. 

2) Another approach is to have a field that can be selected on the document called "Redaction Changes Needed"  (with an optional field to add a reason). Then you can use workflow to grant that user to the see through redaction right to this specific document. We generally add a timer onto this workflow that removes this right after 15 minutes automatically. This gives them plenty of time to make and save any redaction changes they need. 

This 2nd approach also works well as a Business Process if you don't care about the reason, or want to use a list of generic reasons (i.e. you create multiple copies of the BP that say something like "Need to redact XXX" ). This sort of thing is actually pretty common in other systems for things like social security numbers, and is usually audited to make sure it's not being abused. 

Many times we've actually combined these two - someone does all of the initial metadata entry and redacts items then later there's a system that if someone has a buisness reason to see the redacted items they can grant themselves access with the knowledge that they are being tracked. 

My assumption is that certain data within a document has become sensitive and they would like to minimize risk of that information being shared in the future by using redactions. However that data should now also be hidden from regular staff in the long term but in the short term they would like regular non privileged users to be able to perform that redaction rather than rely on superusers (with the see through redactions right) to do this.

It does seem slightly odd in that a user is effectively permanently redacting data they can currently see, but then not see it again. If the redaction was made in error then it would be difficult to correct.
 

Hi,

One of my client also has requested for the same functionality, ability to redact and never see through them. They are a law firm and need it as a part of their privacy policy. I understand that they can see it when the document is initially scanned but it is more like a precautionary policy as they would like to minimise the possibility of a breach. 

Is there a particular way in which we can achieve this ?

Thank you.

Bipin Nambiar

I am following this post. I also have a customer that needs to be able to redact, but not able to see already redacted documents in the same folder. Please let me know if there is a work around that does not require moving to different folders.