Monitoring checkout/checkin

I also recommend changing the default to Check In to Yes upon closing a document. 

We had an issue with users keeping documents checked out for months at a time because the default was "No" - by changing the default to "yes" to check in automatically, we have less offending users and less issues. 

The only other comment I have on this is what I've termed "NULL" check-in documents or "Version 0 documents" - there isn't a way presently for Admins to run an easy report of documents that were created (version 0), but were never checked in (Version 1)

This means we have employees who may have created a document, never checked in, and then left the organization and their laptops were wiped. This means the server is holding a spot for an ID that will never be checked in to become version 1. I question performance because I have since deleted some classes, and these Classes still show up in grouping levels because there's Version 0 document(s) associated with it....

I also recommend changing the default to Check In to Yes upon closing a document. 

We had an issue with users keeping documents checked out for months at a time because the default was "No" - by changing the default to "yes" to check in automatically, we have less offending users and less issues. 

The only other comment I have on this is what I've termed "NULL" check-in documents or "Version 0 documents" - there isn't a way presently for Admins to run an easy report of documents that were created (version 0), but were never checked in (Version 1)

This means we have employees who may have created a document, never checked in, and then left the organization and their laptops were wiped. This means the server is holding a spot for an ID that will never be checked in to become version 1. I question performance because I have since deleted some classes, and these Classes still show up in grouping levels because there's Version 0 document(s) associated with it....