When you open a policy document stored in OneDrive for Business, Word may display it as read-only and disable AutoSave. This prevents you from editing the document and saving changes directly. The root cause is often a combination of file permissions, document metadata, or OneDrive sync state. This article explains why Word opens policy documents as read-only and provides step-by-step fixes to restore AutoSave and editing capabilities.
Key Takeaways: Restoring AutoSave and Editing for Policy Documents
- Word > File > Info > Check for Issues > Inspect Document: Removes read-only metadata and document properties that trigger Protected View.
- OneDrive settings > Sync and backup > Manage backup: Verifies Known Folder Move is active so Desktop, Documents, and Pictures sync correctly.
- SharePoint site permissions > Site settings > Site permissions: Ensures you have Edit or Contribute access to the document library containing the policy file.
Why Word Opens Policy Documents as Read-Only and Disables AutoSave
Word uses AutoSave only when the document is stored in OneDrive or SharePoint and you have edit permissions. Policy documents often have metadata or settings that make Word treat them as read-only. Common triggers include:
The document has been marked as final or restricted by the author. Word reads the “Mark as Final” flag and disables editing and AutoSave. Policy documents may also contain ActiveX controls, embedded macros, or digital signatures that trigger Protected View. When Protected View is active, Word opens the file as read-only and AutoSave is turned off.
Another cause is the OneDrive sync state. If the file has a sync conflict or is not fully downloaded, Word may open a local cached copy that is read-only. Finally, SharePoint document libraries can enforce read-only access through permission levels or versioning settings, such as requiring checkout before editing.
Marked as Final vs Protected View
The “Mark as Final” feature sets a property that informs Word the document is complete. Word then displays a yellow bar at the top and disables editing. Protected View is a security feature that opens files from untrusted locations without editing rights. Both prevent AutoSave from starting.
OneDrive Sync Conflicts
When two users edit the same file, OneDrive creates a conflict copy. The original file becomes read-only until the conflict is resolved. Similarly, if the file is still uploading, Word may show it as read-only temporarily.
Steps to Restore AutoSave and Edit Policy Documents
- Enable AutoSave in Word
Open the document in Word. Look at the top-left corner of the window. If AutoSave is toggled off, click the toggle switch to turn it on. If the toggle is grayed out, the file is not stored in OneDrive or SharePoint. Move the file to a synced OneDrive folder. - Remove the Mark as Final flag
Go to File > Info. If you see a yellow bar saying “Marked as Final,” click the Edit Anyway button. This clears the flag and re-enables editing and AutoSave. - Exit Protected View
If a yellow bar says “Protected View,” click Enable Editing. Word then treats the file as trusted and AutoSave becomes available. - Check document properties for restrictions
Go to File > Info > Check for Issues > Inspect Document. In the Document Inspector, uncheck all options except Document Properties and Personal Information. Click Inspect. If the inspector finds restricted metadata, click Remove All. Save the file and reopen it. - Verify OneDrive sync status
Open OneDrive from the system tray. Check the file status. A green checkmark means the file is synced. A red X indicates a sync conflict. Right-click the file and select Resolve conflict. Choose to keep either the server version or your local version. - Check SharePoint permissions
If the document is stored in a SharePoint library, open the library in a browser. Click the document name and select Manage access. Confirm your account has Edit or Contribute permissions. If not, contact the site owner to grant access. - Disable the Require Check Out setting
In SharePoint, go to the document library settings. Under Versioning settings, set Require Check Out to No. This allows multiple users to edit the file without checking it out first. Changes take effect immediately.
If Word Still Opens Policy Documents as Read-Only
Word Shows a Red X on Shared Office Files
A red X in OneDrive means the file has a sync error. Right-click the file in File Explorer and select View sync problems. OneDrive opens a list of errors. Common fixes include renaming the file to remove invalid characters or moving it out of the OneDrive folder and back in.
AutoSave Is Grayed Out for All Documents
This indicates Word is not connected to OneDrive. Sign in to Word with the same account used for OneDrive. Go to File > Account and verify your account appears under User Information. If not, click Sign In and enter your Microsoft 365 credentials.
Document Opens in Read-Only Mode on a Shared Computer
If you are using a computer where another user is signed into OneDrive, the file may be locked. Sign out of the other account in OneDrive settings. Then sign in with your own account and reopen the document.
Policy Document Contains ActiveX Controls or Macros
Word may block editing for security reasons. Go to File > Options > Trust Center > Trust Center Settings > ActiveX Settings. Select Disable all controls without notification. Then reopen the file. For macros, go to Macro Settings and choose Disable all macros with notification. You can then enable macros individually when prompted.
AutoSave vs Manual Save: Key Differences for Policy Documents
| Item | AutoSave Enabled | Read-Only Mode (AutoSave Disabled) |
|---|---|---|
| Save behavior | Saves changes automatically every few seconds | You must use Save As to create a new copy |
| Conflict handling | Word merges changes when multiple users edit | Only one user can edit at a time |
| Version history | AutoSave versions appear in version history | Only manual saves appear |
| File location required | Must be in OneDrive or SharePoint | Any location, including local folders |
| Permission required | Edit or Contribute on the library | Read access is sufficient |
Use the steps in this article to restore AutoSave and editing for policy documents. Start by checking the Mark as Final flag and exiting Protected View. Then verify OneDrive sync status and SharePoint permissions. If the issue persists, inspect document properties for restrictions. For policy documents stored in SharePoint, disabling Require Check Out can prevent read-only issues for all users.