How to Publish a Final Document in SharePoint
Publishing turns a draft into the official, current, trusted version. Done well, it’s clear to everyone what the source of truth is.
What it is
Publishing a document means moving it from ‘draft’ status to ‘official’. In SharePoint terms, this often means creating a major version (1.0, 2.0), updating metadata to reflect approved status, possibly moving the file to a ‘Final’ or ‘Published’ library, and notifying the audience that the new version is live.
The reason ‘publishing’ deserves its own card is that it’s where most teams break down. Documents get approved, but no one tells anyone. Or they get moved to a ‘Published’ folder, but the old draft link is still in the team wiki. Or the new version is live, but three people are still emailing around the previous version. Publishing is fundamentally a communication problem, not just a file-moving problem.
A clean publishing process has three components: the document is in the official location with the official metadata, the audience knows where to find it (and trust it), and old/superseded versions are clearly retired. If any one of these is missing, you have not really published — you’ve just saved another file.
When to use this
- When a document has been approved and is ready for general use.
- When you’re updating a previously published document with significant changes.
- When you need to communicate a new policy, procedure, or template to a wide audience.
- When you’re finalising a piece of work and need to make it accessible to others.
How to do it
- Confirm the document is approved and the latest version is correct.
- Update the document’s metadata to reflect ‘final’ status (e.g. Status = Approved, Version = 2.0).
- Publish a major version if your library uses major/minor versioning.
- Move the file to the official ‘Final’ or ‘Published’ library if your process separates draft and final locations.
- Update navigation, links, or wiki entries to point to the new version.
- Notify the audience with the link to the published version (Teams post, email, intranet announcement).
- Retire or archive the old version so nobody mistakes it for the current one.
Best practices
- Publish one source of truth, not multiple copies. The official version lives in one place; everywhere else links to it.
- Use clear status metadata. ‘Approved’, ‘Effective from [date]’, ‘Next review [date]’. These are fields, not just words in the filename.
- Lock down the published library to read-only for most users. Editors can update, viewers can read. Stops accidental edits to live documents.
- Always communicate publishing. A document nobody knows exists isn’t published. It’s a file in a folder.
Common mistakes
- Forgetting to retire old versions. Two ‘current’ policies in two locations is worse than no policy at all.
- Publishing without notifying anyone. The team keeps using the old version because they don’t know there’s a new one.
- Publishing to a folder nobody can find. If the published location isn’t in your standard navigation, it might as well not exist.
The Governance Starter Kit gives you the plain-English governance system for real organisations. The 5 governance domains, the Roles & Responsibilities Matrix, the Library Standards Audit, the Monthly Governance Routine — and the 5-day Start This Week plan.
Get the Governance Starter Kit — $29 →FAQ
How do I publish a final version in SharePoint?
If versioning is set to major and minor, check in the file as a Major version (e.g. 1.0 instead of 0.5). The major version becomes visible to readers. If content approval is enabled, the document also needs to be approved before publication completes.
What’s the difference between publishing and sharing a SharePoint document?
Publishing changes the document’s status from draft to released — visible to everyone with read access to the library. Sharing grants access to specific people who didn’t already have it. A document can be published but not shared (visible to library members only) or shared but not published (a specific person can see the draft).
How do I unpublish a SharePoint document?
Two options: check in a new minor version (e.g. 1.1) which hides the document from readers until the next major version; or use ‘Unpublish’ if it’s a Communication Site or page. For libraries without major/minor versioning, you’d need to delete or restrict the document directly.
Why isn’t my published SharePoint document showing for everyone?
Three usual causes: the document is checked in as a minor version (drafts are hidden from readers); the document is pending content approval; or the reader doesn’t have permission to the library at all. Check check-in version, approval status, and permissions in that order.