Redaction workspace basics
Tutorial: open the redaction workspace, start a session, mark content, and export a redacted file.
Sessions and files
This tutorial walks through Document Redaction as if you have not used it before. Redaction work is grouped into sessions. One session usually holds one document (or a small set) that you redact and then export.
- Make sure you are in the right organisation and, if your org uses them, the right matter, so new sessions land in the correct place.
- Open the header tools menu and choose Document Redaction (it may appear as Redact on smaller layouts).
- You should see a list of existing sessions (it may be empty the first time). Use the control to start a new session or upload a file, depending on what your screen shows.
- After you add a file, open the session to work on it. Move through pages, add redaction boxes, and save as you go. If your organisation keeps session history, you can return later from the same list.
The format you will use most often is PDF. Depending on your subscription, you may also be able to upload images and process multiple files at once as a batch. Very large bundles are easier if you split them into several sessions or use folders (covered below). See the pricing page for format and volume details on each plan.
Manual and AI-assisted detection
Manual redaction works on every subscription. You draw rectangles (or use the tool your UI provides) exactly where you want content hidden. Nothing is sent through an automated detection step for that path. This is the approach to use when you need full control or when AI features are off.
If your organisation's subscription includes it, you can turn on optional AI-assisted detection. When it is on, Ghost can suggest regions that might contain personal data. You still review every suggestion and adjust or remove boxes before you export. Details for your DPIA appear in our Privacy Policy under document processing.
- Run or accept detection only if your admin has enabled it and your policy allows it.
- Scan the page and confirm or fix each suggestion.
- Never treat the export as final until you have checked the full document yourself.
Review and export
- Use the page navigator and zoom controls to read every page the way a recipient would.
- Turn individual redactions on or off, resize boxes, and use any review or comment features your workspace shows.
- When you are satisfied, use Export to download the redacted file or to attach it to a privacy request case elsewhere in Ghost.
Saving. A floating save-status pill sits at the bottom-right of the canvas. It shows the current state of your work: Unsaved changes, Saving…, Saved Xs ago, or Save failed, retrying…. Click the pill at any time to force an immediate save. Ghost also autosaves in the background when it detects changes, so you do not need to save manually unless you want to.
If your browser crashes or you close the tab before a save completes, Ghost keeps a local draft in your browser storage. The next time you open the same session, it offers to restore your unsaved redaction changes so you do not lose work.
For the processing paths described in our privacy documentation, final rendering for export can happen in your browser. That is normal, but it means very large files need a stable browser session, and strict offline policies may require extra checks with your IT team.
Folders and organisation
When you have many sessions, folders help you group them (for example by matter, team, or stage of a privacy request).
- Look for folder or organise controls on the document list screen.
- Create a folder with a name your team will recognise (such as a matter ID).
- Move sessions into the folder or create new sessions inside it, if the UI allows.
Exact placement of buttons can change between versions, but the idea is always the same. For advanced features such as AI detection, batch processing, and session status workflows, see Advanced redaction techniques.
Where your documents live
Ghost is not intended to be a long-term file archive for your documents. In cloud-assisted sessions, encrypted uploads may be stored to support processing and resume flows. Session metadata (titles, page counts, masked previews in the UI, and similar) may also be stored so you can resume work.
For official wording for security reviews, use the Privacy and Security pages linked from Resources.