Document versions

Update the document. Keep the deal intact.

Replace a file and the room link already in circulation opens the current version, while history and analytics stay connected to the same document record.

A stable document path held in place while the file changes
One document record

Replace the file while its room placement stays fixed.

The current version stays under the same room link and in the same section. Recipients do not need a correction email or a new destination.

Q3 board pack.pdf · Version historyOwner view
Q3 board pack.pdfCurrent · v4
Current document

Q3 board pack

The updated forecast is live in the same place the board already uses.

Version 4Uploaded today · 21:42
A controlled replacement

The update changes one thing: the document.

New filenames and new links fork the room’s history. A RoundOS replacement preserves the address, the earlier versions and the viewing record around them.

01 · Replace

Upload the corrected file.

It becomes the current version of the existing document record.

02 · Preserve

Keep the link already sent.

The room and its document placement do not move when the source file changes.

03 · Continue

Read activity as one timeline.

Analytics stay attached across versions instead of starting again from zero.

Several document states held inside one continuous version history
Version history

Open the earlier file when you need the exact record.

RoundOS keeps prior versions available to the room owner, with the uploader and time of each replacement. You can inspect what changed without relying on filenames like final_v7.

Visibility and continuity

Choose what recipients see. Keep what the room knows.

A document can present only the current version or keep earlier versions available. Either way, the room preserves which version was viewed and when.

01Current only

Keep the recipient experience focused on the latest approved file.

02Previous visible

Leave earlier versions available when the review process needs comparison.

03Analytics retained

See engagement before and after the update in one document timeline.

Earlier document activity joining the current version in one continuous record
RoundOS vs another link

Keep version history attached to one room placement.

New file, new link

Old copies keep circulating and analytics restart.

The recipient has to decide which message and which attachment is now authoritative.

RoundOS versions

One room placement always resolves to the intended file.

The owner keeps the version record while the existing room link remains useful.

Questions

Document versions, answered.

01Do existing room links open the new version?

Yes. Replacing the file updates the document record already addressed by the room link.

02Can I open an earlier version?

Yes. The owner can open retained versions from the document’s version history.

03Can recipients see earlier versions?

You can keep the recipient experience on the current version or leave prior versions visible when the process calls for it.

04Do analytics reset after a replacement?

No. Activity remains connected to the document record across versions.

05Can I tell which version someone viewed?

Yes. The room record keeps the viewed version with the corresponding activity.

A current document continuing the path established by its earlier version
Same link, current file

Update the next document on the same room link.

Keep every recipient on the intended version and every view in one history.

No credit card. Live in minutes.