SharePoint versioning configuration tool

Configure SharePoint versioning settings in bulk, without touching every library

SharePoint versioning keeps a copy of a document every time it changes, so teams can track history and restore an earlier state when needed. Each version is a full copy of the file, not just the changed part, which is why version history is one of the biggest drivers of SharePoint storage growth. Document libraries default to keeping up to 500 major versions, and lists default to 50.

Getting these settings right, such as version type, retention limits, content approval, or check-out requirements, means you must open Library Settings on every single library or use PowerShell. You can manage site-level settings with commandlets such as Set-SPOSite, while tenant-wide defaults require tenant-level configuration, including Set-SPOTenant. Neither approach scales once you're managing dozens of libraries across multiple sites, site collections, or farms.

SharePoint Manager Plus provides centralized management features that apply version history, retention, and access-control rules in bulk across on-premises SharePoint and SharePoint Online. It also includes scheduling controls, so settings stay consistent without repeated manual work.

Key features that simplify versioning configuration

Bulk configuration across farms and tenants

Apply the same versioning rules across on-premises farms and SharePoint Online tenants from one console instead of configuring each library manually.

Full control over major and minor versions

Configure major and minor versioning, then define how versions are retained by setting version count limits, draft limits, and activity-based expiration.

Content approval and draft visibility controls

Configure content approval, control draft item visibility for readers, editors, or approvers, and require document check-out before editing, all alongside your versioning settings.

Scheduled, recurring enforcement

Run configuration now or schedule it to run automatically, with email notification on completion, so versioning settings don't drift out of policy over time.

Common versioning configuration scenarios

Standardizing settings after a migration

When you migrate libraries from another site, they often arrive with inconsistent or default versioning. Apply a single standard configuration across all of them in one task.

Getting ahead of a storage quota

Set major version counts and define an automatic or manual time limit across libraries to control the growth that version history quietly causes.

Enforcing governance policy tenant-wide

Roll out a required content-approval and check-out policy across every site rather than relying on individual site owners to configure it correctly.

Keeping configuration consistent over time

Schedule the task to run periodically so new libraries and any manually changed settings are brought back in line automatically.

How SharePoint Manager Plus compares with native SharePoint

Benefits of managing versioning settings with SharePoint Manager Plus

• Keep storage growth under control: Standardize version limits and trimming rules across libraries, addressing one of the biggest drivers of SharePoint storage consumption.
• Enforce governance consistently: Apply content approval, draft visibility, and check-out rules the same way everywhere, instead of trusting each site owner to configure them correctly.
• Work across every supported SharePoint environment: Manage versioning settings for SharePoint Online and on-premises 2019, 2016, 2013, and Subscription Edition from a single console.
• Reduce admin dependency: Enable technicians to configure versioning settings, modify permissions, and more, without elevating native privileges.

How to configure versioning settings in SharePoint

Apply versioning settings across your environment in a few steps:

1. Navigate to Management > Document Management > Versioning Settings.
2. Under Select Farm/Tenant, choose your SharePoint farm or tenant to configure.
3. Enter a Task Name, and add a description if needed.
4. Under Version Management and Retention, set Document Version History to No Versioning, Create major versions, or Create major and minor (draft) versions.
5. Set a Version time limit, such as No time limit, Automatic (versions expire based on activity and file age), or Manual (delete versions older than a set number of days).
6. Set a Version count limit by entering the number of major versions to keep, and optionally enable Keep drafts for the following number of major versions.
7. Under Content Visibility and Control, choose whether to require content approval for submitted items, which users can see draft items in the library (any user who can read items, only users who can edit items, or only users who can approve items), and whether to require check-out before editing.
8. Under Schedule Settings, set Operation Mode to Run Now or Schedule for recurring enforcement, and optionally enable Email Notification.
9. Click Apply.

Features that complement Versioning Settings

If you are managing SharePoint governance and document policy at scale, SharePoint Manager Plus provides several other features that complement the Versioning Settings tool:

• Clear Version History: Reclaim storage from the existing versions before new retention rules take effect, so trimming policies apply to a clean baseline.
• Check-In Documents: Release checked-out files across libraries, so a newly enforced check-out policy doesn't inherit stale locks from the old configuration.
• Edit Document Metadata: Populate approval and status columns across a library, so content approval workflows configured through Versioning Settings have the metadata they need to route documents correctly.
• Permission Management: Pair versioning governance with permission audits to enforce a complete document control policy—who can access what, and how those changes are versioned and approved.