OneDrive Admin Checklist: Word AutoSave opens read-only for policy documents

When users open a Word policy document from OneDrive or SharePoint, AutoSave may be grayed out and the file opens in read-only mode. This behavior often occurs because the document is set as a policy document, a template, or has restrictive permissions applied. This article explains why policy documents open read-only, how to adjust settings to allow editing, and provides a checklist for administrators to resolve the issue.

Why AutoSave Is Disabled for Policy Documents

Policy documents are often stored in SharePoint libraries with special settings. These settings can prevent AutoSave from activating. The most common causes are:

Check-Out Requirement

If a SharePoint document library requires check-out before editing, Word opens the file in read-only mode. The user must manually check out the file to enable editing and AutoSave. This is a deliberate security measure to prevent simultaneous edits on sensitive documents.

File Marked as Final or Template

A document marked as “Final” by the author or saved as a Word template (.dotx, .dotm) opens in read-only mode. AutoSave is disabled because the file is not a standard .docx or .docm document.

Permissions and Sensitivity Labels

Microsoft Purview Information Protection sensitivity labels can restrict editing. If a policy document has a label that limits access or editing rights, AutoSave will be disabled. Similarly, if the user only has read permissions on the SharePoint site, the file opens read-only.

Group Policy or Registry Settings

Administrators can disable AutoSave via Group Policy or registry keys. If the setting “Disable AutoSave” is enabled, AutoSave is turned off for all documents, including policy documents.

Checklist to Enable AutoSave for Policy Documents

Follow these steps in order to identify and fix the cause of read-only AutoSave for policy documents. The checklist is designed for Microsoft 365 administrators.

1. Check the SharePoint library check-out setting
   Go to the SharePoint document library that contains the policy document. Select the gear icon > Library settings > Versioning settings. Under “Require Check Out,” ensure it is set to “No” if you want users to edit without checking out. If you must keep check-out enabled, inform users to click the check-out button in the toolbar before editing.
2. Verify the file type
   Confirm the policy document is saved as a .docx or .docm file. If it is a .dotx or .dotm template, save it as a .docx. Open the file in Word, go to File > Save As, and choose “Word Document (docx).” This enables AutoSave.
3. Review sensitivity labels
   In the Microsoft Purview compliance portal, go to Information protection > Labels. Check if the label applied to the policy document has encryption or user rights that limit editing. If so, modify the label to allow editing for the intended users, or apply a different label that does not restrict editing.
4. Check user permissions
   Ensure the user has at least Contribute or Edit permissions on the SharePoint document library. Go to the library, select the gear icon > Library permissions. If the user only has Read permission, change it to Contribute or Edit.
5. Inspect Group Policy for AutoSave
   On a user’s computer, open the Local Group Policy Editor. Navigate to User Configuration > Administrative Templates > Microsoft Word 2016 > Word Options > Save. Check if “Disable AutoSave” is set to “Enabled.” If so, set it to “Not Configured” or “Disabled.” This setting can also be managed via Cloud Policy for Microsoft 365.
6. Enable AutoSave in Word Options
   Ensure AutoSave is turned on in Word. Go to File > Options > Save. Check the box “AutoSave files stored in the cloud by default in Word.” This setting enables AutoSave for all new and existing cloud-based documents.
7. Clear the Mark as Final flag
   If the document is marked as Final, open it in Word, go to File > Info > Protect Document, and select “Mark as Final” again to uncheck it. This removes the read-only flag and re-enables AutoSave.

If AutoSave Still Does Not Work After the Checklist

OneDrive Sync Client Blocks AutoSave

If the policy document is synced via OneDrive and the sync client is paused or has errors, AutoSave may not work. Check the OneDrive icon in the system tray. If it shows a red X or a paused icon, resume sync or resolve errors. Go to OneDrive settings > Account > Choose folders, and ensure the folder containing the policy document is synced.

Document Is Opened in Protected View

Word opens documents from untrusted locations in Protected View, which disables editing and AutoSave. If the policy document is from an external source or an email attachment, click the “Enable Editing” button in the yellow bar at the top of the document. To prevent this, add the SharePoint site to the Trusted Locations list in Word Options > Trust Center > Trust Center Settings > Trusted Locations.

Third-Party Add-Ins Interfere

Some add-ins can disable AutoSave. Open Word in Safe Mode by holding the Ctrl key while starting Word. If AutoSave works in Safe Mode, disable add-ins one by one in File > Options > Add-Ins. Restart Word after disabling each add-in to identify the culprit.

AutoSave vs Manual Save: Key Differences for Policy Documents

Item	AutoSave Enabled	AutoSave Disabled (Read-Only)
Description	Saves changes automatically every few seconds to the cloud	User must manually save using Ctrl+S or File > Save
File type	Works only with .docx and .docm files stored in OneDrive or SharePoint	Applies to .dotx, .dotm, .doc, .rtf, and local files
Check-out requirement	Requires the file to be checked out if the library requires check-out	File opens read-only; user must check out manually
Permissions needed	At least Contribute or Edit permissions on the library	Read permission is sufficient to open but not edit
Mark as Final	Does not work; file opens read-only	Read-only is enforced regardless of AutoSave setting

Policy documents that require editing should have AutoSave enabled. If the document must remain read-only for most users, consider using a separate editing workflow with a staging library that does not have check-out required. After editing, move the final version to the read-only policy library.

After completing the checklist, users can open policy documents with AutoSave active. Verify the setting by opening a policy document and checking that the AutoSave toggle in the top-left corner of Word is on. If the toggle is off, click it to enable AutoSave. For documents that must remain read-only by design, consider using a separate read-only library and granting edit access only to authorized editors.