Introduction to Versioning

Why enable versioning?

When versioning is enabled in site lists, you can track and manage information as it evolves. You can look at earlier versions and recover them, if necessary. That is very handy, for example, when people realize that earlier versions of an item might be more accurate than later ones. Some organizations retain multiple versions of items in their lists for legal reasons or audit purposes.

By default, versioning is turned off. To turn it on and implement your versioning decisions, you must either have Full Control or Design permissions.

You might also want to track both major and minor versions of a file. A major version can signal that a document is ready for review by a wide audience, whereas the minor (draft) version is a work-in-progress and not yet ready for wide circulation.

NOTE    Major and minor versions are only available for libraries, not for lists.

Versioning settings – How they work

The Versioning Settings dialog contains three sections for lists and four sections for libraries. Each section requires decisions when you set up a list or library. Of course, if you have the necessary permissions, you can change the settings at a later date.

  • Content Approval   . Use this section to decide whether or not to require content approval for items submitted to the list.

  • Item (or Document) Version History   . Use this section to select the various versioning options that are available to you. The following table lists each option and the impact of choosing it.

NOTE    The Versioning Settings dialog box options differs slightly depending on whether you are working with lists or libraries. The table below reflects options available for both lists and library versioning settings.



Create a version each time you edit an item in this list/document library?

No is the default setting. For lists, If you select Yes, a new version of the item is created each time the item is edited.

For libraries only, you can select Create major versions or Create major and minor (draft) versions.

Keep the following number of versions

If the check box for this optional setting is selected, the number below it indicates how many versions of the item are retained in the list. If, for example, that number is 25, the oldest version is deleted when the 26th version is created. Then, only versions 2-26 are available.

Keep drafts for the following number of major/approved versions

This option applies only when Yes is selected in the Content Approval section and in theItem/Document Version History section of the Versioning Settings dialog. If that is the case, you can determine the number of drafts that you want to keep for each major or approved version. Unless you have a legal or otherwise special requirement, you probably don’t need to retain all drafts for each version. You might, for example, opt to retain drafts for only the most recent five versions.

  • Draft Item Security section   . Use this section to determine who should see drafts of items that are not yet approved.

    IMPORTANT    The set of options in this section are only available when the Content Approval section is set toYes.

    You can allow any user who has Read permissions to the list to view the drafts, or you can restrict the view to only those users who can edit items or to only the author of the item and the people who can approve items.

  • Require Check Out (for library versioning only)   . Select this option if you want to protect documents in this library from being modified by multiple users at the same time. Users will have to check out documents before editing them, and then check them back in when done.

NOTE    If the library will be storing Microsoft Project (.mpp) files that are synchronized with task lists on your site, clear this check box.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk