Turn On Major and Minor Versions in SharePoint: Practical Workflow for Business Users

SharePoint versioning saves copies of your files every time someone edits them. Without versioning, a bad edit or accidental delete can destroy hours of work with no way to undo it. Major versions (1.0, 2.0) are visible to everyone, while minor versions (0.1, 0.2) let you draft changes privately before publishing. This article walks you through enabling both major and minor versioning on a SharePoint document library and explains when each version type makes sense for your team.

What Major and Minor Versions Do in SharePoint

Versioning is a built-in SharePoint feature that creates a numbered snapshot of a file each time someone saves changes. Major versions are whole numbers — 1.0, 2.0, 3.0 — and represent completed, publishable states. Minor versions are decimals — 0.1, 0.2, 1.1, 1.2 — and represent drafts or work in progress.

When you enable minor versions, SharePoint adds a Publish button to the file context menu. A user can save a minor draft, work on it over several days, then publish it as a new major version when the work is final. The version history stores every snapshot, so you can restore any previous version at any time.

Why Use Minor Versions

Minor versions are ideal for content that requires review before release. For example, a legal document might go through three minor drafts (0.1, 0.2, 0.3) before the author publishes it as version 1.0. Reviewers with the correct permissions can see the draft, but regular readers only see the published major version.

Why Use Only Major Versions

Major-only versioning is simpler and works for most internal team files. Every save creates a new major version — 1.0, 2.0, 3.0 — with no draft step. This is sufficient for shared spreadsheets, project plans, and meeting notes where drafts are unnecessary.

Prerequisites

To change versioning settings, you need Edit or Full Control permissions on the SharePoint site. You must be a site owner, site member with the Edit permission level, or a site collection administrator. Versioning is a library-level setting, not a site-level setting, so you configure it inside each document library separately.

Steps to Turn On Major and Minor Versions

1. Open the document library
   Go to your SharePoint site and click on the document library where you want to enable versioning. If you are using a team site, this is typically the Documents library. If you are using a communication site, it may be a custom library name.
2. Access library settings
   Click the gear icon in the upper-right corner, then select Library settings. If you do not see Library settings, click Site contents, find your library, hover over its name, click the three dots, and choose Settings.
3. Open Versioning Settings
   Under the General Settings column, click Versioning settings. This page contains all versioning controls for the library.
4. Enable major and minor versions
   In the Content Approval section, select Yes for Require content approval for submitted items. This step is required to unlock minor version options. Then, in the Document Version History section, select Create major and minor (draft) versions. If your organization uses content approval workflows, you can skip the approval requirement and still enable minor versions by selecting Create major versions and then checking Create minor versions on the same line.
5. Set draft item security
   In the Draft Item Security section, choose who can see draft items. The options are:
   – Any user who can read items: All users with read access can see minor versions. Use this only when drafts contain no sensitive information.
   – Only users who can edit items: Only site members with Edit or Contribute permissions can see drafts. This is the recommended default for most business teams.
   – Only users who can approve items: Only users with the Approve permission level can see drafts. Use this for highly confidential documents that require formal review.
6. Limit the number of versions stored
   Under the Version History section, check Keep the following number of major versions and enter a number such as 100 or 500. Then check Keep drafts for the following number of major versions and enter a number such as 10 or 50. This limits storage consumption. When the limit is reached, SharePoint automatically deletes the oldest version each time a new one is created.
7. Require check out (optional but recommended)
   In the Require Check Out section, select Yes to force users to check out a file before editing it. This prevents two users from editing the same file simultaneously and ensures that minor drafts are saved to a user’s check-out copy rather than overwriting the published version.
8. Save your settings
   Click OK at the bottom of the page. SharePoint applies the changes immediately. Existing files in the library will not have version history until the next time someone edits and saves them.

Common Mistakes and Limitations

Version History Is Not Retained for Existing Files

Enabling versioning does not retroactively create version history for files already in the library. Only edits made after the setting is turned on generate versions. If you need a baseline snapshot of current files, ask users to open each file, make a trivial change such as adding a space, and save it. That action creates version 1.0 for each file.

Content Approval Is Not the Same as Publishing

Content approval and minor version publishing are separate features. Content approval adds a pending status that an approver must manually approve before the file is visible to all readers. Publishing a minor version to major does not automatically trigger approval. If you need both workflows, enable content approval and minor versions together.

Storage Limits Can Fill Up Quickly

Each version stores a full copy of the file in SharePoint, not just the changes. A library with 500 files and 100 versions per file can consume significant storage. Set version limits conservatively — 50 major versions and 10 draft versions is usually enough for most teams. Monitor your site storage in the SharePoint admin center under Active sites.

Users Cannot See Drafts After Enablement

If users report they cannot see draft files after you enable minor versions, check the Draft Item Security setting. If you selected Only users who can approve items, only approvers can see drafts. Change the setting to Only users who can edit items to allow all site members with edit permissions to view drafts.

Major and Minor Versions vs Major-Only Versions: Key Differences

Item	Major and Minor Versions	Major-Only Versions
Version numbers	1.0, 1.1, 1.2, 2.0	1.0, 2.0, 3.0
Draft visibility	Controlled by Draft Item Security setting	Not applicable — all versions are visible to readers
Publish action required	Yes — user must publish to create a major version	No — every save creates a new major version
Best use case	Documents requiring review before release	Internal team files and collaboration
Storage consumption	Higher — each minor draft consumes storage	Lower — fewer versions stored per file

Now you can enable major and minor versioning in any SharePoint document library. Start by configuring versioning on a single library used for draft-heavy documents such as proposals or policy manuals. After your team is comfortable with the publish workflow, expand versioning to other libraries. To clean up old versions later, use the Check version history option in the file context menu and delete obsolete drafts manually.