The dietary manager opens the weekly menu rotation, makes a change, saves it, and then realizes she typed over last week's version by accident. Or a policy binder on the shared site gets edited by someone who was not supposed to touch it. Either way, the question is the same: can we get the old one back?
Often the answer is yes, in under a minute, thanks to version history. But version history has limits, and department heads should know where they are before they depend on it.
When versioning is turned on for a SharePoint document library, each save creates a numbered version of the file. The earlier versions are kept, along with who saved them and when. You can open a past version, compare it, or restore it so it becomes the current one.
This is the right tool when a file still exists but its contents are wrong. Typical examples:
Someone overwrote a good document with a bad one
A table in a spreadsheet was deleted and saved
Two people edited the same file and one set of changes was lost
A policy was changed and you need to see what it said before
Open the SharePoint site and find the document in its library.
Select the file, then choose the three dots next to it and find Version history.
Look through the list. Each row shows a version number, the date and the person who saved it.
Open the version that looks right to confirm it is the one you want.
Choose Restore to make it current. The newer versions are not erased. Restoring simply creates a new current version from the older one.
Files stored in Microsoft 365 apps such as Word and Excel often show the same history from within the program, under the file name at the top.
Version history is a good tool for one problem and a poor one for others. Be aware of these limits.
The file has been deleted. If the file itself is gone, the versions go with it. You would first need to recover the file from the SharePoint recycle bin, which holds deleted items for a limited time, and then its versions return along with it.
The entire library or site has been deleted. Deleting a library or site removes its history. Recovery depends on the recycle bin windows and may need an administrator, and past that time nothing is left.
The change is old. SharePoint limits how many versions it keeps, and the oldest may be trimmed once the limit is reached. A busy file that is saved many times a day can cycle through its history quickly. Your administrator can see how many versions your libraries are set to keep.
Versioning was never turned on. In some libraries or older sites it is off, or set to a low number. Ask your IT provider to check.
The damage touched many files. If an attacker or a faulty sync changes hundreds of files, restoring each one by hand is not practical. Large-scale recovery needs a proper backup or the restore tools an administrator has.
A few small practices help a lot:
Edit in the library, not on copies. Files emailed back and forth create many versions that SharePoint does not know are related.
Use clear folder ownership. Decide which department owns the policy binder, the forms library and the schedules, and who may edit them.
Limit edit permissions. Many people need to read a document and few need to change it.
Save meaningful changes. Each version is easier to trust when the changes between them are deliberate.
Check the settings now. Do not wait for a bad day to learn that versioning was off.
It is easy to confuse the two. Version history lives in the same library as the file. If the library is deleted, the account is compromised or the retention window passes, the history can go too. A backup is a separate copy, kept elsewhere, that you can restore even in those cases. The best arrangement uses both: versioning for quick fixes and a backup for the serious ones.
If your care setting keeps policies, schedules or survey documents on SharePoint, ask your IT provider two things. Is versioning on and set to a sensible number? Is SharePoint backed up outside of Microsoft?
UnityCare IT can review your SharePoint libraries for versioning and permission settings, restore files and libraries when something goes wrong, and add an independent backup for the times version history cannot help. We also work with department heads on simple folder structures that people will actually follow.
Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.
Call or text: 405-285-3845
New customers: start@unitycareit.com
Existing customers: support@unitycareit.com
Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas
Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support