Contracts
Agreements, NDAs, and proposals with templates, merge fields, version history, and signatures.
By Sebastian StreiffertPublished Jan 10, 2026Updated May 4, 20267 min read
What you can do here
Contracts holds the documents that bind: agreements, NDAs, proposals, order forms, policies. Each one is linked to the customer it concerns, keeps its version history, and can be signed without leaving Lumenbase.
- Send an NDA and have it signed the same afternoon.
- Generate a proposal from a template with the customer details already filled in.
- Answer "which version did we actually send them?" in one click.
- Get a reminder before a contract auto-renews.
Agreements
4 documents
Legal
4 documents
Commercial
4 documents
People
4 documents
- 1Families: Four groups so the shelf stays navigable
- 2Status: Where each document is in its life
- 3Versions: Every replacement keeps what came before
Document types
| Family | Covers |
|---|---|
| Agreements | Contracts, master service agreements, order forms, amendments |
| Legal | NDAs, data processing agreements, policies |
| Commercial | Proposals, service level agreements, client contracts |
| People | Employment contracts |
Settings → Workspace → Features → Contracts. Turning one off just hides it from the New document picker; documents already created are untouched.Create a document
Write, upload, or generate
Link it to the customer
Fill in the details
| Status | What it means |
|---|---|
| Draft | Still being written. Not in force. |
| Active | In force. |
| Superseded | Replaced by a newer one. |
| Expired | Ran past its end date. |
| Terminated | Ended early. |
| Archived | Out of the working list, still on the record. |
Save time with templates
A template is a document with blanks in it. Generate it against a customer and the blanks fill themselves in: company name and website, the contact's name and email, the deal name and value, your own workspace name, and today's date.
Anything that could not be filled is listed by name after generating, so an empty counterparty is something you see rather than something you send. You can also mark a spot as needs input when a human has to make a decision there.
Keep the history straight
Uploading a replacement makes it the current version and keeps the old one. The version list shows who uploaded each, when, the dates it applied, and a note on what changed.
- Download the original file, or a PDF or Word copy.
- Restore an older version. It comes back as a new version rather than erasing what happened.
- Archive a document you are done with instead of deleting it.
Get it signed
Add the signers
Send for signature
Watch it come back
| State | What it means |
|---|---|
| Not sent | Nobody has been asked to sign yet. |
| Out for signature | Sent, nobody has signed. |
| Partially signed | Some signers done, waiting on the rest. |
| Executed | Everyone has signed. |
| Declined | A signer refused. |
You can withdraw a request at any point before it completes.
When something looks wrong
| What you see | What to do |
|---|---|
| A type is missing from New document | An admin has it switched off. Ask for it in contracts settings. |
| Generated blanks are still blank | The record was missing that detail. The list after generating names each one. |
| A colleague cannot open a contract | Contracts need their own access, separate from files. Ask an admin. |
| A signer never received the link | Copy the signing link from the document and send it yourself. |
Quick reference
Was this article helpful?
