Editing results
Detection is the start, not the end. The list of mappings a run produces is meant to be reviewed, and the Anonymization Editor is where you do it. This page is a map of the editing tasks; each links to the detail.
The review loop
Section titled “The review loop”- Open the run in the editor. It shows the anonymized result and the full entry list.
- Read the result on the Anonymized view, then sweep the original with Instant redact to catch anything uncovered.
- Fix what’s wrong using the actions below.
- Save to output. The history table updates to match your edits.
The five corrections
Section titled “The five corrections”| The result is… | Do this |
|---|---|
| Over-redacting a value you want to keep | Turn the entry off |
| Wrong — bad span, wrong type, weak fake value | Edit the entry |
| Missing a value the model didn’t catch | Add an entry from a selection |
| Missing a stamp, photo, or signature (no text) | Draw a redaction or blur the image |
| Cluttered with a duplicate or misfire | Remove the entry |
Why edits beat re-running
Section titled “Why edits beat re-running”Re-running the model costs time and has run-to-run variance — it might fix one thing and change another. Editing the result is surgical: you keep the 95% the model got right and touch only what needs touching. And because the editor never re-runs detection, edits are instant and stay on your machine.
Make corrections stick across documents
Section titled “Make corrections stick across documents”If you find yourself making the same correction every time — always keeping your company name, always catching a codename the model misses — don’t re-do it per document:
- Save the editing pattern as a template and apply it to the next similar document.
- Add recurring known mappings to a dictionary.
- Add guidance to your profile’s prompt so future runs catch the value automatically.
The history record reflects your edits
Section titled “The history record reflects your edits”Once you Save to output, the run’s replacement table is updated to your final entries. The audit trail shows what actually went into the delivered file, not just the model’s first pass.