VERSIONS

Work on the next version without touching the official one.

Every file you upload creates a numbered version. NexDok keeps the latest (“Latest”) and the official one (“Published”) apart — your team keeps working while everyone reads the current one.

Try it ↓Talk to us

EVERY VERSION HAS A ROLEv5Latestv4Publishedv1–v3PreviousvNSigned (vN)

TWO VERSIONS SIDE BY SIDE

The one in progress and the one that counts.

While v5 is under review, Search, Ask and downloads keep using published v4. The document page shows both: “Working file” and “Published file”.

v5Working file● Latest

Uploaded by Ana · Oct 20

Editor

v4Published file● Published

Per diem 2026 · Sep 1

Official

v3Previous● Archived

Jun 15

Admins only

v2Previous● Archived

Mar 2

Admins only

SIGSigned (v6)● On signing

PDF imported from SignDok

New version

APIv7 via API● Integration

Uploaded with an “upload” key

Numbered server-side

Stays the same: the published version, until an admin publishes another.

Changes on upload: only “Latest”. The app never overwrites a version.

HOW PUBLISHING WORKS

Publishing is an explicit decision — and it leaves a trail.

1 · UPLOADA new version

An editor uploads the file and the next version is created.

2 · WORKWithout touching the official one

The published version is still the one everyone reads.

3 · PUBLISHAn admin decides

“Publish version v5 · v4 → v5” in one step.

4 · ARCHIVEAutomatically

The previous one becomes “Previous” and the new one is indexed for Search and Ask.

And it holds itself back: no publishing with an active signature or an open approval on that version.

TRY IT — SAMPLE WORKSPACE

Upload, publish and download as each role.

“Travel & Expense Policy” · v1 to v4 · v4 published.

About Editor

Upload new version · travel-policy-2026-10.pdf

v5 · LATEST

Working file · 1.8 MB

v4 · PUBLISHED

Published file · still the official one

Search and Ask still read v4

Sample data.

PROTECTED HISTORY

Every version numbered and in its place.

01Safe numbering

Two simultaneous uploads never get the same number.

02One published version

Publishing archives the previous one automatically.

03A fingerprint per file

Every version stores its SHA-256.

04Controlled downloads

Earlier versions are admin-only, with 10-minute links.

Version history badges

What you see in “Versions (N)”.

BadgeMeansWho changes itRead by Search/Ask

LatestLatest uploaded versionEditor on uploadOnly if none is published

PublishedOfficial versionAdmin on publishYes

PreviousEarlier versionAutomaticNo

Signed (vN)Imported signed PDFSignDokOnce published

HONEST BY DESIGN

What version history does — and doesn’t.

No version compare

There’s no diff view between versions.

No restore

To go back, upload or publish another version.

No overwriting

The app never replaces an uploaded version’s file.

Publishing is for admins

Editors upload; publishing is an admin or owner decision.

THE DOCUMENT PAGE

Working file and Published file, one above the other.

When the latest version isn’t the published one, the page shows both. The “Versions (N)” history shows each one’s role.

Upload new versionPublish v5Versions (5)LatestPublished

Travel & Expense PolicyPublished v4

LATESTv5Oct 20

PUBLISHEDv4Sep 1

PREVIOUS3versions

PreviewDownloadPublish

Publish version v5: v4 → v5

FROM SIGNATURE TO VERSION

The signed PDF comes back as another version.

When SignDok finishes, the signed PDF is saved as a new version of the same document, ready to publish.

Service Agreement 2026

v3 · SIGNED (v3)

Signed PDF imported from SignDok

v2 · PREVIOUS

service-agreement-2026.docx

Not published automatically — an admin decides

Upload

Editor role or higher.

Publish

Admin or Owner role.

Up to 25 MB

Per file.

Always on

Versioning needs no setup.

Which document changes every month?

We’ll show you how to work on the next version without touching the current one.