Best Practices for your SharePoint Document Library: Require Check Out

Today's best practices recommendation, brought to you by Mindsharp via the Power End User course I attended last month, has to do with why you should require check out in your document libraries, and how to go about doing so.

The reason that it's recommended that you require check out on the documents in your library is that, unless you do so, multiple users will be able to check out and edit a single document at the same time*, and without any indication that another user is already editing the same document.  What do you think happens if two people are making changes to the same document at the same time?  If you said, "whoever saves first wins," give yourself a gold star.

Such headaches can be avoided by requiring that users check out a document from a library before making changes.  Don't worry, if someone has checked out a given document and is in the process of making changes, a read-only version can still be accessed by other users.

Is it a complicated or laborious process to set up a document library to require check out?  Not at all.  In fact, setting up a document library to require check out is as simple as selecting a single radio button in the library settings:

To navigate to the above setting, from within the library itself, first select Document Library Settings from the Settings dropdown, then select the Versioning Settings hyperlink under the General Settings header.  From there, you'll be presented with the setting options page for the library, and you'll notice that the last option is Require Check Out.  Once you're here, all you need to do is switch the defaulted Require Check Out radio button selection from No to Yes (as pictured above), click OK at the bottom of the page, and you're all set.

* Please see Kyle Bakker's helpful comment below for an instructive clarification of this process.


Posted Sep 08 2008, 03:35 PM by John Anderson

Comments

Paul wrote re: Best Practices for your SharePoint Document Library: Require Check Out
on Mon, Nov 3 2008 9:49 AM

I have a Quality Manual on Sharepoint. I have the only authority to change documents. How can I prevent anyone from Checking Out a document? If someone needs a document or form, and they accidently check it out, then I cannot ever edit it. Can I allow people to Read Only and not be able to check out a document?

John Anderson wrote re: Best Practices for your SharePoint Document Library: Require Check Out
on Tue, Nov 4 2008 5:04 PM

Hiya, Paul - thanks for writing.  Good news!  Not only is "yes" the answer to your question, but since it wasn't something that I'd addressed previously, I went ahead and dedicated today's blog entry to documenting the process for you:  community.bamboosolutions.com/.../marking-the-contents-of-a-sharepoint-document-library-as-read-only.aspx

Kyle Bakker wrote re: Best Practices for your SharePoint Document Library: Require Check Out
on Mon, Nov 10 2008 12:56 PM

Can I offer some friendly clarification.

Your wording in the second paragraph may confuse some people. (multiple users will be able to check out and edit a single document at the same time), I would use the term locked for editing, since checked out implies that the document has been checked out by another user and must be checked in, even if they close the doc.

If you do not check out a docuement, but open it in edit mode- it will lock it from editing for a short period of time. If the other user trying to edit a doc has office 2003, it wont tell them its locked for editing by another user, it will just open it read only even if they choose edit. If they have office 2007 it will give a prompt that its locked by the other user and it can only be opened it edit mode, however, it will eventually time out and other users will be able to edit it.

For this reason, I typically prefer to instruct users to check out documents if they are going to work on them for longer than a few minutes or the documents are not of a critical nature. I give the owner of the library the option. I always turn on versioning however so recovery of overwritten changes is possible. If the business rule is to always check out documents because of sensative content or other reasons or if the users of the documents decide they want to check them out I force checkout. Its faster to go through the check out- in process if its forced, because it prompts you automatically.

There is a good article on Checkout here

office.microsoft.com/.../HA101314791033.aspx

sumanth wrote re: Best Practices for your SharePoint Document Library: Require Check Out
on Wed, Nov 12 2008 9:39 AM

We have recently set this 'Require Check Out' to true in our Sharepoint. And we have a web application that uses sharepoint as the document management system and uploads files to the sharepoint. Since setting the 'Require Check Out' to true, we were having problems because after uploading, a file has to be checked in and there is no way to do that currently. Any ideas or pointers.

Thank you in advance.

John Anderson wrote re: Best Practices for your SharePoint Document Library: Require Check Out
on Mon, Nov 24 2008 3:11 PM

Kyle, thank you very much for your thoughtful clarification.  I've updated my post, instructing readers to read your comment.

sumanth, I started looking into your question, and have made some inquiries on your behalf, but I think I'm going to need a little more information from you before I can proceed further.  I'm assuming that you're looking to automate the checkin process (since manual checkin should certainly be an option) ... if yes, is there not an available method in your Web app which will address the checkin when it makes its call to SharePoint?

P.S.  I should note that I began my investigations into sumanth's question by visiting the Microsoft article on Checkout that Kyle recommended.  Thanks again, Kyle!

Add a Comment

(required)  
(optional)
(required)  
Remember Me?

About John Anderson

John Anderson is new to both Bamboo Solutions and to SharePoint, but he isn't new to online community.  Having recently departed AOL, where he was a Programming Manager for that company's social media team, John is thrilled to have joined the Bamboo family as Manager of Content & Syndication.  As a member of the Online Operations team, John takes great pride in helping shape the creation and direction of Bamboo Nation, our nascent SharePoint community.  Within Bamboo Nation, John writes the blog SharePoint Blank, in which he (always candidly, sometimes humorously, and even occasionally informatively) documents his daily progress in learning SharePoint.  John is also profoundly uncomfortable writing about himself in the third person and is going to stop now.

  
Bamboo Solutions Corporation, 2002-2008