SharePoint version history helps users inspect, restore, and audit earlier versions of documents. Version limits also control how much historical data a library retains.
This guide explains how to configure versioning for an individual SharePoint Online document library.
Before changing the settings
Determine:
- How many versions users genuinely need
- Whether drafts or minor versions are required
- How long older versions should remain available
- Whether retention or legal requirements apply
- Whether the library inherits organization or site-level defaults
Reducing version limits can eventually remove older versions. Review the existing settings and recovery requirements first.
Open the versioning settings
- Open the SharePoint site.
- Open the required document library.
- Select Settings.
- Select Library settings.
- Open Versioning settings.
You need sufficient site or library permissions to change these options.
Choose the versioning behaviour
Major versions
Major versioning records published versions such as 1.0, 2.0, and 3.0. This is suitable for most collaborative document libraries.
Major and minor versions
Minor versioning also records drafts such as 1.1 and 1.2. Use this when documents follow a formal drafting and publishing process.
Version limits
Set a limit that balances recovery requirements with storage consumption. SharePoint supports organization, site, and individual-library version limits. A library can inherit its version-history policy or use a separate configuration for its specific content requirements.
Decide whether approval is required
The library can require content approval before a document becomes visible as an approved major version. Enable this only when the business process has defined reviewers and ownership. Approval requirements can create unnecessary delays in ordinary team libraries.
Control draft visibility
If minor versions are enabled, choose who can see drafts:
- Any user who can read items
- Users who can edit items
- Users who can approve items and the document’s author
Use the most restrictive option that still supports the library’s workflow.
Save and test the configuration
- Review the versioning and visibility options.
- Select OK to save.
- Edit a test document several times.
- Open the document’s menu.
- Select Version history.
- Confirm that the expected versions appear.
- Test restoring a previous version.
A version-history configuration is useful only if users and administrators can successfully recover a document when required.
Understand how limit changes affect existing versions
Microsoft distinguishes between count limits and expiration settings:
- A new expiration setting applies to versions created after the setting changes.
- When a version-count limit is reduced, SharePoint gradually removes older versions as files receive new versions.
- Existing versions are not necessarily trimmed immediately.
Administrators who need to align existing content with new limits can use SharePoint Online PowerShell and version-trimming jobs.
Version history is not a complete backup
Version history is valuable for correcting edits and restoring earlier files, but administrators can change its limits and retention behaviour. Organizations with formal recovery requirements should also maintain an independent Microsoft 365 backup and tested restoration process.
