Use shared-file editing and resolve save conflicts

Calc’s shared-file mode combines saved edits to the same desktop spreadsheet and asks you to resolve overlapping changes. It is not browser coauthoring, and it restricts commands that are normally available in an ordinary workbook.

Check whether shared mode fits

This guide uses LibreOffice Calc 26.2 desktop with English standard menus on Windows or Linux. It is based on documentation; no concurrent user session or conflict dialog has been natively tested here.

The shared document and its lock file need an already-authorized location where the intended editors can access and update them. This tutorial does not set up server permissions, weaken file security, or invite collaborators. If you do not have an approved two-session practice environment, prepare the local fixture and use the conflict example as a review scenario rather than claiming to reproduce concurrency by opening two ordinary copies.

Before enabling sharing, create SharedPractice.ods. In A1:C3 enter headers Item, Quantity, Unit price; then Bolts, 5, 12; then Washers, 8, 2. Put =B2*C2+B3*C3 in E2, with Total in E1. The initial total is 76. Save a separate backup before the exercise.

Enable and recognize the mode

Choose Tools > Share Spreadsheet, select the sharing checkbox and confirm. Save when asked, because saving activates the mode. The title bar should include (shared).

On opening a shared spreadsheet, read the message about unavailable features. Among the restrictions documented for this version are sorting, defining database ranges, pivot operations, chart editing and many structural changes. Formatting edits such as fonts, colors and number formats are not saved in this mode. Prepare the layout and formulas before sharing rather than planning to redesign the sheet during data entry.

For real use, agree who may resolve conflicting values and how to validate them. Shared mode supplies a conflict mechanism, not a business rule for deciding which quantity is correct.

Distinguish non-overlapping edits from conflicts

In an approved two-session test, both sessions must open the same shared file before the edits below. They are not two separately named review copies.

First try independent changes: session A changes Bolts quantity to 7, while session B changes Washers quantity to 10. Let A save, then B save. The combined expected data is B2=7 and B3=10, producing 104. Calc reports updates from other users when it incorporates non-conflicting saved changes.

For the conflict scenario, start both sessions from that saved state. A changes B2 to 9 and B changes B2 to 11. Let A save first, then B attempt to save. Calc’s Resolve Conflicts dialog asks which version to keep for the overlapping cell. Decide from the agreed source of truth, not from whichever choice is fastest.

If the retained Bolts quantity is 9, the total should be 128. If it is 11, the total should be 152. B3 should remain 10 in both cases. Inspect each conflict before completing the save; blanket decisions are risky when several cells represent unrelated facts.

Recover and finish cleanly

While one user resolves conflicts, another may see a message that saving is locked during a merge. Cancel that save attempt and retry later rather than repeatedly forcing it. After a successful save, inspect the latest combined data and recalculate the control total.

Save and reopen the file to verify the retained values. If the feature restrictions make the planned work impossible, coordinate an end to shared editing before switching the original out of shared mode. For an isolated analysis, save a separately named copy and disable sharing on that copy instead; do not silently remove others’ access to the working document.

For sequential review with separate returned files, use compare and merge instead. That workflow preserves a baseline and recorded changes without pretending that independent copies are one concurrently shared file.

Official references

• LibreOffice documentation 1