Workflow guide · works alongside LEAP, not integrated with it
Using Omitly with LEAP.
Redact a document held in a LEAP matter — permanently, on your own machine. Export it, redact it in Omitly, import the result back. No upload, no plugin, no integration.
Omitly is a standalone desktop app and is not integrated with, endorsed by, or affiliated with LEAP Legal Software. This guide describes a manual, local file-handling workflow between two independent products — there is no plugin, API connection, or automated sync. It's for solo and small-firm practitioners running LEAP on Windows who need a redacted version of a matter document without uploading it anywhere.
The workflow, in four steps
Omitly never talks to LEAP directly. You move the file out, redact it locally, and put the result back — the same way you'd hand a document to any other desktop tool.
- 01
Export the document from the matter
In the matter, open the Details & Correspondence tab, select the document, then right-click and choose Export Document as PDF. Save it to a local folder you'll remember — not a LEAP-internal location. (LEAP updates its interface from time to time; if the wording differs on your build, look for the equivalent export-to-PDF action.)
- 02
Redact the document in Omitly
Open the exported PDF in Omitly and apply your redactions. Omitly permanently removes the underlying text in the redacted areas — it does not draw a black box over text that stays recoverable underneath. On save, Omitly defaults to the same folder as the original with .redacted added to the name; then choose Save certificate to write the redaction certificate alongside it.
- 03
Check the output files
Confirm both files sit next to your original: the redacted PDF and its certificate. Your document and certificate never leave your machine in this workflow — they're generated on local disk and stay there unless you move them.
- 04
Import both files back into the matter
Back in LEAP, on the same Details & Correspondence tab, right-click in the correspondence list and choose Import → Import Document (or drag both files onto the matter). Import the redacted PDF and the certificate as two separate matter documents. If the Import menu differs on your build, dragging both files onto the open matter window does the same thing.
Recommended file naming
LEAP's correspondence list sorts by name, date or type — it doesn't group related files automatically. Keep the original filename as a prefix so the redacted PDF and its certificate sort next to the original when you're scanning the list later.
| File | Name |
|---|---|
| Original (exported from LEAP) | SmithAffidavit.pdf |
| Redacted output | SmithAffidavit.redacted.pdf |
| Certificate | SmithAffidavit.redacted.certificate.pdf |
Why this workflow is safe
Your document never leaves your machine at any stage — export, redact and import all happen on local disk. Omitly has no account to sign in to and sends no content telemetry.
The certificate is a signed, tamper-evident record of the redaction. It lets anyone you send the redacted PDF to independently confirm the file hasn't been altered since you sealed it, and check exactly which regions were removed — verification is over the document's content, not its filename, so the certificate stays valid even if the file is renamed or moved. That is an integrity check the recipient can run themselves, not a guarantee from LEAP or any third party, and it is not a LEAP feature or a LEAP-verified output.
Frequently asked questions
Is Omitly integrated with LEAP?
No. Omitly is a standalone desktop app and is not integrated with, endorsed by, or affiliated with LEAP Legal Software. There is no plugin, API connection, or automated sync — you export the document from the matter, redact it locally, and import the result back yourself.
Does my document get uploaded when I redact it?
No. Omitly redacts on your own machine. In this workflow the document and its certificate are generated on local disk and stay there — there is no upload of the document and no content telemetry.
Why import the certificate back into the matter too?
The certificate is a signed, tamper-evident record of the redaction. Keeping it in the matter alongside the redacted PDF means anyone you later send the file to can independently confirm the redacted PDF hasn't been altered since you sealed it, and check exactly which regions were removed.
The menu wording is different in my LEAP version — is the guide wrong?
LEAP updates its Desktop interface from time to time, so exact labels can differ between builds. The two actions that matter are exporting the document to PDF and importing it back into the matter; the precise menu path is secondary.
How should I name the files so they stay together in LEAP?
Keep the original filename as a prefix — e.g. SmithAffidavit.pdf, SmithAffidavit.redacted.pdf, SmithAffidavit.redacted.certificate.pdf. LEAP's correspondence list sorts by name, so all three sort together and it's clear which redacted file and certificate belong to which source document.
New to permanent redaction? How to redact a PDF so the text can't be recovered →
Redact a matter document without it leaving your desk.
Try Omitly free for 14 days. Remove the content, keep a certificate that proves what was removed — all on your own machine.
Join the waitlist