Locking for the files your team actually edits

Latch checks a file out on SharePoint the moment you start saving it, and checks it back in once the upload has landed. No drive mapping, no replacement sync client, no per-application plugins.

The problem

SharePoint has had check-in and check-out for twenty years, but the OneDrive sync client ignores it. Applications are expected to integrate it themselves, and almost none ever have. So teams working on binary files — drawings, models, spreadsheets that cannot be co-authored — either live with sync conflicts and “copy” files, or replace the sync client entirely.

What Latch does

Latch runs alongside the sync client you already have. It watches for local editing activity under your synced libraries, checks the file out on the server, waits for the sync client to finish uploading, and then checks it back in. Colleagues see the file as checked out to you, using SharePoint's own enforcement — not an advisory flag Latch invented.

• Saved changes land under a lockCheck-out happens at first save, and is released only after the upload is confirmed on the server.
• Whole-session protection where possibleApplications that maintain their own lock files — AutoCAD and LibreOffice among them — are protected from open to close.
• Real server-side enforcementA second user's write is refused by SharePoint itself, not merely discouraged.
• Never touches your file contentLatch does not move, copy, upload or modify files. The sync client owns the bytes.

What it does not do

We would rather be precise than impressive. Most Windows applications perform no file activity at all between opening a document and saving it, so for those, protection begins at first save rather than at open. Modern Office formats are deliberately excluded, because Word, Excel and PowerPoint support real co-authoring and an exclusive lock would fight it. Latch is a Windows product today.

How Latch handles your data and credentials →

Contact