How NetDocuments ndSync Handles Editing Conflicts: A Complete Guide

When multiple team members work on the same documents across different locations and devices, conflicts are inevitable. NetDocuments’ ndSync tool handles these scenarios gracefully, ensuring no work is lost while maintaining document integrity.

What is ndSync?

ndSync is NetDocuments’ file synchronization application that provides Dropbox-like functionality for legal professionals. Users can sync workspaces, folders, and documents to their local computer (Windows or Mac), work offline, and have changes automatically synchronized back to the cloud when they reconnect.

ndSync is NetDocuments’ file synchronization application that provides Dropbox-like functionality for legal professionals. It allows users to sync workspaces, folders, and documents to their local computer (Windows or Mac), enabling them to work offline and have changes automatically synchronized back to the cloud when they reconnect to the internet.

A Common Conflict Scenario

Here’s how a typical conflict develops:

1. User A checks out a Word document using ndOffice and begins editing
2. User A saves changes but keeps the document checked out
3. User B, working offline or from their local ndSync folder, opens the same document (the version from before User A’s edits)
4. User B makes and saves their own changes

Now two users have edited the same document with different changes—a conflict.

How ndSync Resolves the Conflict

ndSync prioritizes data preservation while respecting document checkout status. When it detects a conflict, it uses “unofficial versions” to ensure no work is lost.

The resolution process:

1. Conflict Detection — ndSync recognizes that User B’s changes conflict with User A’s because the document is checked out or has been modified on the server
2. Unofficial Version Created — ndSync automatically converts User B’s changes into an unofficial version and saves it to the server
3. User Notification — User B receives a bubble notification that their edits are being saved as an unofficial version
4. Continued Editing — As long as User B keeps the document open, additional changes save to that unofficial version

What Happens When Both Users Close Their Documents

When the locally edited document is closed:

• The unofficial version remains on the user’s computer
• The file is renamed to indicate its status (e.g., “Document_unofficial.docx”)
• An unsynced overlay icon appears on the file
• The official version syncs down from the server
• Future changes to the local unofficial version will not sync to the server

Key Takeaways

ndSync strikes a balance between flexibility and data integrity. By respecting checkout status and preserving all changes through unofficial versions, it ensures every team member’s contributions are preserved and accessible.

Conflicts aren’t failures—they’re natural in collaborative work environments. What matters is having a system that handles them gracefully.