Contact

LibreOffice Calc · Sharing, safety and accessibility · Intermediate

Recover earlier document versions and protect file access

Practice recovery of stored Calc versions, protect an ODS copy with an opening password, and inspect Description and Custom Properties before a document handoff.

Documentary author review; no native application testing claimed · Editorial standards

Calc can store earlier versions inside an ODS document and can require a password to open a saved file. These solve different problems: a version helps recover prior content; an opening password limits access to the file’s contents.

Create a recoverable checkpoint

Use LibreOffice Calc 26.2 desktop with English standard menus on Windows or Linux. The steps are documentary, not a native-tested recovery or encryption demonstration. Practice with synthetic information and retain an ordinary backup before experimenting.

Create VersionPractice.ods. Enter Budget in A1 and 1000 in B1. Enter Revision note in A2 and Initial estimate in B2. Save the file.

  1. Choose File > Versions.
  2. Click Save New Version.
  3. Enter a useful comment such as Baseline: budget 1000 before supplier revision and confirm.
  4. Save the document itself. The stored version belongs inside this ODS file; it is not a separate cloud-history item.
  5. Change B1 to 1200 and B2 to Supplier revision, then save another named version and save the file again.

A comment should explain what makes a version worth returning to. “Version 2” alone does little to distinguish a validated checkpoint from an accidental intermediate state.

Open the earlier content safely

Return to File > Versions, select the baseline entry and choose Open. Calc opens the earlier version as a read-only copy. Verify B1=1000 and the initial note. The current document should still contain 1200; viewing a version is not the same as replacing the working file.

To recover a usable earlier document, save the read-only version under a new recovery filename rather than overwriting the current file immediately. Check the recovered budget and note before deciding which file should become your working copy.

There is an important consequence: Save As does not carry the old stored versions into the new file, according to the guide. Preserve the original ODS containing the version list if that history matters. Avoid the Versions dialog’s Delete control during recovery; it deletes the selected stored version without another confirmation.

Add an opening password to a separate copy

For the access-control exercise, return to the current original VersionPractice.ods and verify B1=1200 and B2=Supplier revision, not the recovered baseline copy. Choose File > Save As, name the new file ProtectedPractice.ods, retain OpenDocument Spreadsheet format, and select Save with password. Save, then enter and confirm a password you can retain securely. Do not use an actual account password or put the password in the workbook itself.

Close the protected copy and reopen it. Verify that opening requires the password, then enter the correct password and inspect B1. A sheet-protection password is not an equivalent check: sheet and cell protection controls editing, not whether the file’s contents can be read.

Because Save As creates a new file without the old stored versions, do not assume this encrypted copy also contains the original version history. If you need future checkpoints inside the protected document, save new versions in that document and verify their presence separately.

Verify and plan recovery

Change the protected practice budget from 1200 to 1250, save, close and reopen with the password. Confirm 1250. A correct password prompt is not enough if you accidentally protected a different file.

To remove opening protection from a practice copy, open it with the correct password, use Save As and clear Save with password. Treat the resulting file as unencrypted and keep it only where that is acceptable. This is not a password-recovery technique for a file whose password is lost.

Stored versions, backup copies and AutoRecovery are separate mechanisms. Inspect your configured backup paths and recovery settings rather than assuming they guarantee recovery from deletion or corruption. Keep a separate backup of important files, including the original version-bearing ODS, and verify you can open that backup before relying on it.

Inspect document properties on a handoff copy

Continue in Calc 26.2 desktop, English standard menus on Windows or Linux. This is a documentary exercise: the checks below have not been run in Calc, and no saved-file, privacy or screenshot validation is claimed. Other releases, macOS and alternative interfaces are outside this procedure.

Close ProtectedPractice.ods after the 1250 checkpoint. In your file manager, copy it to a separate MetadataPractice.ods; keep both ProtectedPractice.ods and the version-bearing VersionPractice.ods untouched. Open only the metadata copy with its password. Before editing, check its filename, B1=1250 and B2=Supplier revision. Keep this practice local rather than sending it to anyone.

Choose File > Properties. Inspect General for the filename, location and type, plus any identifying information in Created, Modified and Last printed. Note whether such information exists, not real names. Review every populated Description field, including Contributor, Publisher and Comments, and every Custom Properties row’s name, type and value. A template may have supplied rows; do not assume the list is empty. These controls are documented in Calc Guide 26.2, Chapter 1, “Using document properties”.

Use this synthetic handoff record:

  1. On Description, set Title to Budget handoff practice and Subject to Training only. These are document properties, not instructions to rename the file or edit cells.
  2. On Custom Properties, confirm PracticeCode does not already exist. Click Add Property and create that name with a text-compatible type and value REVIEW-01. Leave unrelated fields alone. If that name is already present or the text value cannot be entered, stop rather than overwrite or force a conversion.
  3. Confirm the dialog with OK, save, close and reopen MetadataPractice.ods. Inspect File > Properties again and compare the first checkpoint below.
  4. Change only PracticeCode to REVIEW-02; confirm, save, close and reopen. Compare the second checkpoint.
  5. Remove only the PracticeCode row using its red X button. Confirm, save, close and reopen once more. Compare the final checkpoint; a blank value is not the same as an absent row.
Checkpoint after reopening Title Subject PracticeCode
Initial record Budget handoff practice Training only REVIEW-01
Revised record Budget handoff practice Training only REVIEW-02
Removed practice field Budget handoff practice Training only No row with this name

At each checkpoint, also require the password prompt, the correct filename, B1=1250 and B2=Supplier revision. The table is an independently checked specification of the intended field changes, not observed Calc persistence. Unrelated custom rows should remain as they were; do not remove them just to match an empty-list expectation.

If the copy opens without a password, stop and recreate it from the verified protected original. If a value reverts, confirm you reopened the metadata copy and saved after accepting Properties. If the budget is 1000 or 1200, you started from the wrong checkpoint: close without saving further edits and recreate the handoff copy from the verified protected original. If a required tab/control differs, stop and consult documentation for your installed version rather than changing global User Data or security settings.

Metadata inspection is separate from version recovery and encryption. Do not use Reset Properties as a cleanup shortcut. Removing this one practice field does not certify that personal data, cell contents, comments, stored versions or exported metadata are gone. Unexpected identifying information requires a separate review before any real handoff; this exercise makes no sanitization guarantee.

Official references