Document Revision Management in SharePoint: Versioning, Approval and Publishing

SharePoint document revision management: major and minor versions, check-out, content approval, draft visibility, revision numbers and the effect of version limits on storage.
Technical summary
Technology
SharePoint Online, Versioning, Content Approval, PnP PowerShell, Power Automate
Topic
Versioning, approval and publishing for controlled documents
Level
Intermediate
Prerequisites
  • Full control permission on the document library
  • The organization’s document control procedure
  • PnP PowerShell (optional)
In this article7 sections

For controlled documents such as procedures, instructions, forms and technical drawings, the auditor’s question isn’t “where is the file?” The question is “which version is current and who approved it?”, and the answer is hidden in the library settings. SharePoint Online provides four building blocks for this: major and minor versions, required check-out, content approval and draft visibility. These four don’t work when turned on separately; they need to be set up together. Below, we explain this setup, its effect on storage and how the revision number is reflected in the document, for quality owners and SharePoint administrators.

Version history settings: major and minor versions

There are two versioning models in a document library. In the major-versions-only model, each save increments 1.0, 2.0, 3.0, and everyone with read permission sees every version. In the major and minor versions model, working copies are minor versions such as 1.1 and 1.2 (drafts); the “Publish a major version” action raises it to 2.0.

Model Suitable content Limitation
Major versions only Team working documents, meeting notes There’s no distinction between draft and published
Major and minor versions Procedures, instructions, policies Users need to know the publishing step
Major/minor versions + content approval Controlled documents subject to audit Requires an approver role and process discipline

In corporate intranet solutions, the natural choice for a controlled document library is the major and minor versions model: the major version corresponds to the “published revision”, and minor versions to the preparatory work on that revision. But know this: SharePoint’s version number is a technical counter. There’s no guarantee it will match the organization’s Rev. 03 one to one. If a major version is rolled back or a restore is done, the SharePoint number advances but the corporate revision doesn’t. We come back to this distinction in the revision number section below.

The settings are made on the “Versioning settings” page in the library settings. To make the setup repeatable and documentable, we use PnP PowerShell:

Connect-PnPOnline -Url https://contoso.sharepoint.com/sites/quality -Interactive `
  -ClientId <app-registration-client-id>

Set-PnPList -Identity "Procedures" `
  -EnableVersioning $true -EnableMinorVersions $true `
  -MajorVersions 100 -MinorVersions 5 `
  -EnableModeration $true `
  -DraftVersionVisibility Approver `
  -ForceCheckout $true

Get-PnPList -Identity "Procedures" |
  Select-Object EnableVersioning, EnableMinorVersions, MajorVersionLimit,
    MajorWithMinorVersionsLimit, EnableModeration, DraftVersionVisibility, ForceCheckout

The parameter most often confused in the field is -MinorVersions: it specifies for how many major versions drafts are kept, not the number of minor versions. Choose the values according to the organization’s policy; SharePoint Online enforces a minimum for the major version limit at the library level (100 for a long time) and rejects lower values. The -ClientId in the connection is the Entra ID app registration you created for PnP PowerShell in your tenant. Don’t skip the Get-PnPList line at the end of the script. Thinking a setting was written isn’t the same as seeing it was written.

Balancing check-out and co-authoring

Required check-out makes the user who will edit the document reserve the file for themselves first. It prevents two people from making different changes at the same time; a change comment can be requested at every check-in. The cost is co-authoring: in a library with required check-out, Word, Excel and PowerPoint files can’t be edited by several people at once. You can’t have both.

The decision criterion is the document’s lifecycle:

  • If preparation involves several authors, the draft is prepared with co-authoring in a separate working library; the final text is moved to the controlled library with required check-out.
  • If there’s a single responsible author, required check-out is used directly in the controlled library.
  • For technical drawings (formats without co-authoring support, such as CAD), check-out is the only built-in way to prevent conflicts.

The known side effect of required check-out is the “forgotten check-out”: the user reserves the file, goes on leave and the document stays locked for weeks. Those with full control over the library remove the lock with the “Discard check out” command in the file menu. For this, prepare a control view listing files whose “Checked Out To” column isn’t empty, and look at it weekly. There’s one more trap: newly uploaded files that have never been checked in are visible only to the person who uploaded them. These files are taken ownership of from the “Manage files which have no checked in version” page in the library settings. If a user says “I uploaded it but nobody can see it”, that’s the first place to look.

Content approval and draft visibility

When content approval is turned on, every major version goes into Pending status and isn’t visible to readers until the approver says Approved or Rejected; readers continue to see the last approved version. The approval right is in permission levels that include the “Approve Items” permission; among the defaults, Full Control and Design carry this permission. Since the Design level can be hidden on new sites, it’s cleaner to define a custom permission level that adds only this permission for approvers. Gather approvers in a separate SharePoint group; the approval right is then separated from site ownership.

Draft visibility (draft item security) offers three options:

Option Who sees drafts Use
Anyone who can read All readers Not suitable for controlled documents
Those who can edit Those with edit permission In-team review
Those who can approve and the author Approvers and the document’s author Controlled document library (requires content approval)

Built-in content approval is single-step and writes who approved it to the version history. If a preparer–reviewer–approver chain, parallel approval or reminders on timeouts are needed, a Power Automate flow comes into play. For flow design, see the approval processes with Power Automate guide. In this setup, the flow should end with a step that updates the built-in approval status when approval is complete. Otherwise two separate approval records are created and in an audit you have to explain which one is valid. On the implementation side, our Power Automate approvals and automation service page can be used as a reference.

Revision number and the document header

In an audit, the revision number, effective date and approver must be visible on the printed or PDF copy. The SharePoint version number sits in the “Version” column of the library; it isn’t written into the document automatically. The options:

Method How it works Watch out for
Corporate revision column The “Revision” and “Effective Date” columns are filled in at the moment of approval Risk of error when filled in by hand; filling it with a flow is safer
Word document property field In Word, the column is linked to the header via Insert → Quick Parts → Document Property Only for Office files; must be prepared in the template
PDF generation on approval A flow generates a PDF from the approved version and copies it to a publishing library Two copies are created; the distinction between source and published must be clear
SharePoint version only The Version column is used as the reference Not visible on the printed copy; may not match the corporate number

The setup that causes the fewest problems in the field is this: “Revision”, “Effective Date” and “Approved By” fields linked to the header in the content type’s Word template, and an action in the last step of the approval flow that fills these columns. A revision number entered by hand gets entered wrong sooner or later. For content type and site column design, see the metadata and content type guide.

Version limits and the effect on storage

Every version takes up space from the tenant storage quota. Since new versions can be created at short intervals in Office files with AutoSave on, the history of large files swells quickly. An example calculation: 100 versions of a 20 MB technical drawing take up about 2 GB; if there are 200 files of this size in the same library, the versions alone can reach about 400 GB. This calculation shows the upper bound; actual consumption depends on how the file size changes between versions. When a quota warning arrives, this is often the first place to look.

To manage storage:

  • Library-based limit: Let policy determine the number of major versions kept for controlled documents; a lower limit can be used for working libraries.
  • Organization- and site-level version history limits: SharePoint Online offers automatic or manual version cleanup options based on version count or age. Since the options and defaults change over time, verify the current state in Microsoft’s version history limits documentation.
  • Interaction with retention policies: On a site covered by a retention policy or label, deleted or changed content is kept in the Preservation Hold Library and takes up quota. Lowering the version limit doesn’t remove the retention obligation.

Lowering the version limit doesn’t always delete existing excess versions immediately; cleanup may require a separate operation. For controlled documents, old revisions are audit evidence. Before cleanup, confirm the quality management system’s retention requirement in writing. If approved versions will be shown in an audit, define the evidence owner and access permissions within the scope of audit evidence management with SharePoint.

Controlled document library checklist

  • Major and minor versions are on; the number of major versions kept is based on a written policy.
  • Content approval is on; draft visibility is “those who can approve and the author”.
  • Approvers are in a separate SharePoint group; they don’t have to be the same people as the site owners.
  • The decision on required check-out was made together with the need for co-authoring.
  • The revision, effective date and approver columns are defined in the content type and linked to the template header.
  • If an approval flow is used, it also updates the built-in approval status.
  • Monitoring views for pending approvals and forgotten check-outs are ready.
  • Quality and IT have jointly approved the relationship between the retention policy and the version limit.
  • It has been verified with a test user that readers see only the approved version.

The last item is skipped in almost every project. Once permissions are set up, opening the library with a read-only test account and seeing that drafts aren’t visible is the only practical proof that the settings interact correctly. A test done with an admin account proves nothing. For setting up reader and approver groups, the SharePoint permission model guide is complementary. All steps from setting up a controlled document library to going live are within the scope of our SharePoint document and revision management service.

Frequently asked questions

Can the SharePoint version number be used as the corporate revision number?

Don’t use it directly. The SharePoint version number is a technical counter that also advances with operations such as restores. It’s more reliable to keep the corporate revision number in a separate column and fill it in at the moment of approval.

Does requiring check-out prevent co-authoring?

Yes. In a library with required check-out, Office files can’t be edited by more than one person at the same time. A separate working library for multi-author preparation strikes this balance.

Do readers see draft versions?

If content approval is on and draft visibility is set to “approvers and the author”, users with read permission see only the last approved major version. Always verify this behavior with a test account.

Does lowering the version limit reduce storage immediately?

Not always. Cleaning up existing excess versions may require a separate operation; content covered by a retention policy also continues to stay in the Preservation Hold Library.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Web

We build and maintain corporate websites, WordPress and CMS platforms, intranet and SharePoint portals, document management, and form and approval workflows, and keep them secure and up to date.

Knowledge Center

Other articles