Automate redaction · Autessa Redact
Bulk document intake
Autessa’s bulk intake turns one uploaded .zip of documents into rows ready for automated redaction. Each file is streamed to storage with its content hash, email attachments become their own rows linked to their parent, and an interrupted intake resumes without ingesting anything twice.
The problem
A delivery of ten thousand files
Large document sets arrive as archives: an export, a discovery production, a migration. Bulk intake is the front door that turns that archive into a table of records your redaction pipeline can work through, safely and resumably.
- Expands a .zip into rows of a table you choose, streaming each entry rather than loading the archive at once.
- Maps the stored file, name, path, content hash, size and type to columns, plus fixed values on every row.
- .eml entries are expanded so their attachments become their own rows, linked to the parent email.
- File types and a size limit can be set; skipped entries are reported one by one rather than failing the whole intake.
- Crash-safe and resumable: progress is checkpointed, and a retry skips entries already inserted.
- Optional indexing for semantic search, and an uploads table that records each archive’s status and count.
How it works
How does bulk document intake work in Autessa Redact?
Upload the archive
Put the .zip in Autessa storage.
Run intake
Bulk Intake expands it into rows, usually as a work queue item for big archives.
Process the rows
Your pipeline extracts, detects, locates and burns each document.
Check the report
The result lists rows created, entries skipped and any per-entry errors.
Every option
Intake options
| Option | What it does |
|---|---|
| columnMapping | fileColumn (required), nameColumn, pathColumn, shaColumn, sizeColumn, mimeColumn, extraStatic. |
| parentShaColumn | Links an email attachment to its parent. |
| allowedExtensions / maxEntryBytes | What is accepted; others are skipped and reported. |
| enableIndexing | Index rows for semantic search as they land. |
| uploadsTableId | One lifecycle row per archive. |
| chunkSize, batchEntriesPerRun, timeBudgetSeconds | How a large archive is split into resumable slices. |
Permissions
Who can do what?
| Who | Can |
|---|---|
| Builders (roles that can create tools and scripts) | Run bulk intake into tables they can write to. |
Connected
How it connects to the rest of Autessa
FAQ
Questions about bulk document intake
Can Autessa redact documents in bulk?
Yes. Bulk intake turns a .zip of documents into rows, and a pipeline built from the document tools redacts each one automatically.
What if an intake is interrupted?
Run it again. Intake is checkpointed and idempotent, so entries already inserted are skipped and nothing is ingested twice.
Are email attachments handled?
Yes. .eml entries are expanded so each attachment becomes its own row, linked back to the email.
100% customizable, code and all
Make Autessa Redact fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours