What is UnitVault?
Hash-verified document storage attached to a listing. The "evidence layer" of a Haubot deal.
Every listing on Haubot has its own UnitVault — a private document store that travels with the equipment. Photos and videos go on the public listing page; documents — inspection reports, ownership papers, invoices, export forms, technical manuals — live in the vault and follow stricter rules.
The vault solves four real problems:
- "Where do I put the inspection report so the right buyers see it?"
- "How do I prove what I disclosed if a buyer disputes it later?"
- "How do I share sensitive paperwork without giving it to every random visitor?"
- "How do I make sure the file the buyer downloaded is exactly the file I uploaded?"
The shape of a vault
A vault contains files. Each file has:
- A category — Inspection reports, Ownership documents, Service history, Invoices, Export documents, Technical documents, Manuals, Serial-number photos, Videos, Other, Internal notes.
- An access level — Public, Sign-in required, Approval required, or Internal only. (See Access levels for the rules.)
- A title — what buyers see in the file row. Optional; if you don't set it, the vault prettifies the original filename.
- A description — a short note buyers see for the public-facing access tiers.
- A SHA-256 content hash — computed by Haubot's servers when the file is uploaded, never trusted from the client.
What you can do as a seller
The vault page on a listing's dashboard (/dashboard/listings/{id}/vault) gives you three blocks:
- Files — add, edit metadata, replace, delete (soft-delete, recoverable), restore.
- Access control — review buyer requests for restricted documents and approve or deny them, with optional expiry.
- Snapshots — lock the current state of the vault into an immutable, hash-verified record. See Document snapshots & verification.
You can also download the entire vault as a ZIP (manifest + README + every file you have access to), or grab a hash-anchored package of a specific snapshot.
What buyers see
On the listing's public page, buyers see a "Documents" block. The block shows only files they're allowed to see — files at access level Internal only are filtered out at the database query, never sent to the buyer's browser. For each visible file the buyer gets:
- The file's title and a short description if you provided one.
- File type, size and upload date.
- A download button (for files they're entitled to).
- A details panel exposing the SHA-256 hash so they can verify the file later.
If a buyer needs a file at Approval required, they click "Request access" and write a short message. You see the request in your dashboard and decide.
What's intentionally NOT in the vault
The vault is for documents — not the listing's marketing media. Photos and videos that buyers see on the public listing page (the gallery, the hero shot, the walkaround video) are managed separately, with watermarking applied automatically. The vault is for the paperwork that backs the deal, not the imagery that sells it.
A note on safety
We accept a strict whitelist of file types. You'll see the list in the upload dialog. The server checks each file's actual bytes against its claimed type — a renamed .exe won't pass as a PDF. ZIP archives are inspected for nested executables, scripts and zip-bomb patterns before they're accepted. Macro-enabled Office files (.doc, .xls, .docm, .xlsm) are not accepted; modern OOXML formats (.docx, .xlsx) are. This is on purpose.


