Documents

E-signature inside your company suite

Upload a PDF, place the fields, and send a link. The signer needs no account. Every signature keeps the exact wording, the file hash, the time, and the address, and the signed copy carries a record page.

Mutual NDA

Version 3
Page 4 of 4Sent to alex@example.com

Alex Rivera

Signature

2026-09-19

Date

I agree that my typed name is my electronic signature and that I have read this document.

Record page: signed at 15:30 UTC from 203.0.113.7, wording v1, SHA-256 9f2c…e41a

Key features

Everything a signature needs, and nothing you have to set up twice

A library with versions

Upload a PDF one time. Each replacement is a new version with its own SHA-256, and every request names the version it carried.

Fillable fields

Place a signature, initials, text, date, or checkbox on the page. A PDF with its own form seeds the fields for you.

Send a link

One email, one link. The link expires when you say. One reminder goes out by itself, and you can send more by hand.

Sign or decline

The signer reads the file in the browser, signs in place with a draw-to-sign pad, or declines with a reason.

Evidence that holds up

The verbatim consent text and its version, the file hash, the time, the IP address, the browser, and the first open, all on the record page.

You hear about it

Signed, declined, or expired: the sender gets the news in the inbox, by email, and in Slack. The signer gets a receipt.

One signing flow, three front doors

The same evidence whether a contractor, a visitor, or a new hire signs

Send it by email

Contracts, waivers, and NDAs go to an address with a link. No account, no app, no printer. The signed copy comes back with a record page.

Sign at the kiosk

Visits shows the documents you pick at check-in. A visitor reads and accepts on the iPad, and the archive records which version they saw.

Benefit Image

Sign inside a playbook

Attach a document to an onboarding step. The new hire signs it as a task, and the archive answers what each employee signed.

For operators and developers

The archive, the kiosk, and the API are part of the same app

One signed archive

Everything signed in the org, newest first: sent by email, at the kiosk, or in a playbook. Filter by source, or look up one person.

A kiosk that keeps records

The Visits kiosk renders the PDF on the device. Each acceptance stores the version, its hash, the wording, and the time.

CLI and API

List templates, send a request, and import each signed form with its receipt and file: orgorg documents requests-list --status Signed.

Send your first document today

Documents comes with OrgOrg. Upload a PDF, place the fields, and send the link.