SharePoint check out stops shared editing
I help organizations to unlock the power of SharePoint
SharePoint Maven explains how check out blocks co-authoring so one person can edit a file at a time.
Key insights
- Check out locks a SharePoint file to one person until it is checked back in.
- Others see a read-only version and a small arrow next to the file name.
- Check-in comments are saved in version history.
- Discard Check Out removes changes made since the file was locked.
- A library can require check out through Versioning settings.
SharePoint Maven Inc recently published a YouTube video explaining SharePoint check out, a feature that stops several people from editing the same file at once. The main takeaway is simple: check out is the opposite of co-authoring, and it is useful when one person needs exclusive control of a document.
The video walks through what other users see while a file is locked, how to check the file back in with a comment, and how to make check out mandatory for a library. It also explains when the feature makes sense and when co-authoring is the better fit.
What's new
The video is not announcing a new feature. Instead, it focuses on an existing SharePoint document-management option that many users may overlook because co-authoring is the default experience for Word, Excel, and PowerPoint files.
SharePoint check out changes that behavior. While a file is checked out to one person, nobody else can change it. They only get the last read-only version, and SharePoint shows a small arrow next to the file name to indicate that the document is locked.
The video also highlights two practical details that matter in day-to-day use. First, a check-in comment is added to version history when the file is returned. Second, all edits made during one check-out become a single version after check-in.
Why it matters
This matters most for admins, site owners, and document owners who need controlled editing rather than live collaboration. If a team works with PDFs, CAD files, contracts, or other files that do not support co-authoring well, check out can prevent confusion and overlapping edits.
It also helps with controlled change processes. If a library requires check out, users must lock the file before editing it, which creates a clear handoff between the person making changes and everyone else who will review them later.
For everyday users, the impact is straightforward: instead of seeing multiple people edit the same file at once, they either wait for the file to be checked back in or work from the read-only copy until editing is allowed again.
The video also points out a downside that admins should consider. Check out is dated compared with co-authoring, so it makes sense only where exclusive editing is actually needed. If a team wants real-time collaboration, check out gets in the way.
How it works
The process shown in the video is direct. You check out the file, edit it, and then check it back in when you are done. SharePoint also lets you discard the check out if you do not want to keep the changes.
- Open the file and use More, then Check out.
- Edit the document while it is locked to you.
- Use More, then Check in, or close the desktop app when prompted.
- Add a comment during check-in so it appears in version history.
- If needed, use Discard check out to throw away changes since the lock began.
The video says the check-in prompt appears when you close the desktop version of Word, Excel, or PowerPoint. It also notes that a site owner can check a file in on behalf of someone else if that person is away and left the file locked.
To make check out mandatory, the video points to the library settings path: Library settings, then More library settings, then Versioning settings, and finally Require Check Out. The video says this applies to metadata edits as well as file content.
Limitations and open questions
The video is clear that check out is not the right answer for every library. It is mainly for documents that cannot co-author, for controlled approvals, and for cases where avoiding OneDrive sync conflicts matters.
One limitation is that all edits made during a single check-out are grouped into one version on check-in, so you do not get separate version entries for each save. That may be fine for some workflows, but it reduces the level of change tracking between edits.
The source material does not say whether the behavior is different across all SharePoint plans or tenant configurations, and it does not provide rollout details. It also does not describe any new admin policy controls beyond the library-level require check out setting.
Sources
- SharePoint Maven Inc video Stop People Editing Your SharePoint File at the Same Time
- SharePoint Maven Inc written guide on checking out a document in SharePoint
Frequently asked questions
What does SharePoint check out do?
It locks a file to one person until they check it back in. Other users can view the read-only version, but they cannot edit it.
Can I undo a check out?
Yes. The video says you can use Discard check out to throw away changes made since the lock began.
How do I make check out required for a library?
The video points to Library settings, then More library settings, then Versioning settings, and Require Check Out.
When should I use check out instead of co-authoring?
Use it when one person needs exclusive editing control, especially for PDFs, CAD files, controlled documents, or workflows that should not have parallel edits.