When you upload multiple documents into a Document Library with versioning turned on, is it a SharePoint 2007 default to keep the documents checked out? For some reason, when multiple documents are uploaded to a document library it doesn't give it a version and keeps the documents checked out to the user that uploaded them. The way it's working is no one can see any of the documents given there is no inital version. The only one that can see the documents is the person who uploaded them. When I looked, I noticed they were checked out to the user that uploaded them. I would think it should function pretty much the same as uploading a single document, where it prompts you for the initial check in after it's uploaded.

If this is a setup issue, is there a way to automatically have the multiple documents uploaded checked in after they are uploaded? Or, is this normal behavior and the users will have to remember to check in the multiple documents after they are uploaded?

Thanks in advance, Robert

  • Have you tried it without check-in required or toggling the major, minor version handling?
    – Tom Resing
    Jun 3, 2011 at 22:01

5 Answers 5


SP 2010: Go to Document Library Settings -> Versioning Settings -> Require Check Out Set to no

MOSS 2007: Document Library -> Settings -> Document Library Settings -> Versioning settings -> Require Check Out Set to no

Also follow this link to have more idea

  • Thanks for the replies. Changing the "Require Check Out" to "no" in the document library worked. Thank you very much for the assistance... Much appreciated... Jun 6, 2011 at 16:23
  • Pleasure to be helpful :). Dec 30, 2011 at 14:31

This is because of having mandatory fields in your Document Library. When you have fields (i.e. Columns) that are mandatory and you upload multiple files, these mandatory columns do not get filled and hence the files are checked out by default.

Quick Solution: Make all mandatory fields (except Name ofcourse) "not required" and try upload multiple files. You will not have the files checked out by default.


Yes that is the default behavior when versioning is enabled in a library.

  • The only other question I have is with the "Require Check Out" option set to "No"; people can edit documents without them being checked out. After they do their edits, will SharePoint require them to check in a major or minor version? Given the document was never checked out to edit, how will it impact versioning with this option set to "no?" Jun 6, 2011 at 17:17
  • When require check out is set to no, people can edit the items without them being checked out. If versioning is enabled, it should ask them if it's a major or minor version when they upload the new copy. I typically feel that if major and minor versioning are going to be used that check out should be required, or else you run into upload collisions and missing data when multiple people try to edit the document in short order. Jun 6, 2011 at 17:40
  • During the document library creation, if I choose "Yes" in the "Create a version each time you edit a file in this document library?" option and set the "Require Check Out" option to "No" in the versioning settings, would the same thing happen in regards to upload collisions and missing data as you described above? Jun 8, 2011 at 16:11
  • Even if the documents aren't required to be checked out for editing, but the other setting creates a new version when a document is edited, wouldn't the versioning with the document library creation setting handle the collisions and missing information? Jun 8, 2011 at 16:20
  • It doesn't do merges, so if User A starts editing a version with Paragraphs 1, 2 and 3 in it and decides to delete paragraph 2, if user B opens the file before any changes are saved back, he'll see paragraphs 1, 2, and 3. If user A saves the file before user B finishes, the current version will have paragraphs 1 and 3. User B makes minor edits to paragraph 1 and saves the file. You're back to paragraphs 1, 2, and 3 again. Forcing check out is the only way to remedy that. Jun 8, 2011 at 16:34

As an addition to Satish Surath's (correct) answer:

Assigning a default value to all of your mandatory metadata fields before bulk-uploading your files will also avoid unwanted check-outs. If you procede like this, you don't have change your column settings to "optional".

You can choose between these two approaches depending on whether or not there are sensible default values for the documents you are about to upload.

  • An addition should be added as a comment and not a new answer Aug 31, 2013 at 11:56

One of your content types may have required field, especially default content type "Document". I changed required field to optional and it worked for me.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.