---
type: concept
title: Collaborative Conflict
tags: [synchronization, data-loss, nextcloud, onlyoffice, collaboration]
related: [nextcloud, onlyoffice, desktop-integration]
created: 2026-07-01
updated: 2026-07-01
sources: ["output/rz_uni_greifswald_de_dienste_webdienste_nextcloud_clients.md"]
---

# Collaborative Conflict

**Collaborative Conflict** refers to the data integrity risk that occurs when a file is edited simultaneously using two different workflows: local synchronization (via a desktop client) and real-time web-based collaboration (via [[onlyoffice]]).

## Mechanism of Conflict
In the context of the Universität Greifswald's Nextcloud implementation, the conflict arises through the following steps:

1. **Web Workflow**: Multiple users edit a document in real-time using OnlyOffice within the browser. Changes are saved instantly to the server.
2. **Local Workflow**: A user opens a synchronized copy of the same file using a local application (e.g., Microsoft Word or LibreOffice), makes changes, and saves the file.
3. **The Collision**: When the Nextcloud Desktop Client synchronizes the local version back to the server, it treats the local file as the current version. Because the local client does not merge real-time collaborative changes, it may overwrite the real-time changes made by other users in the web interface.

## Impact
Because the local application is unaware of the real-time changes happening in the cloud, the synchronization process can lead to **irrevocable data loss** for the users who were editing the file via the web interface.

## Mitigation
Users are cautioned that local synchronization is best suited for individual work or scenarios where external applications are required, while OnlyOffice should be used for active collaboration to avoid data loss.