When finance team members open Word workbooks from OneDrive, AutoSave shows the file as read-only even though they have edit permissions. This issue typically occurs when the workbook is stored in a SharePoint document library that enforces co-authoring restrictions, or when the file is locked by a previous editing session that did not close properly. The read-only state prevents AutoSave from saving changes automatically, which disrupts workflow and risks data loss. This article explains the root causes, provides a step-by-step admin checklist to restore full AutoSave functionality, and covers related issues such as file locks and permission inheritance.
Key Takeaways: Restoring AutoSave for Finance Workbooks
- SharePoint document library > Library settings > Versioning settings: Check that Require Check Out is set to No, which forces read-only for all users except the one who checked out the file.
- OneDrive admin center > Sync > File protection: Verify that Known Folder Move is not redirecting finance workbooks to a personal OneDrive instead of the shared library.
- SharePoint admin center > Active sites > Permissions: Ensure the finance group has Contribute or Edit permission level, not Read, which blocks AutoSave from writing changes.
Why AutoSave Opens Read-Only for Finance Workbooks
AutoSave requires a writable connection to the server. When a Word workbook stored in OneDrive or SharePoint opens as read-only, the file is either checked out by another user, the library requires check-out, or the user lacks write permissions. For finance workbooks, administrators often impose stricter controls such as Require Check Out or limited permission levels to protect sensitive data. These controls inadvertently block AutoSave because the file is not available for simultaneous editing. Additionally, if the workbook was previously opened and not closed gracefully, a temporary lock file may remain on the server, causing subsequent opens to default to read-only.
Require Check Out Setting
SharePoint document libraries have a Versioning Settings option called Require Check Out. When enabled, a user must check out a file before editing. While the file is checked out, all other users see it as read-only. AutoSave cannot save changes because the file is locked to one editor. Finance libraries often enable this setting to prevent conflicting edits. However, it disables co-authoring and AutoSave for anyone who is not the current checkout holder.
Permission Levels
A user with the Read permission level can open files but cannot save changes. AutoSave detects this and opens the file as read-only. Finance workbooks are frequently placed in libraries where the finance team has Read permissions while managers have Contribute or Full Control. If a team member only has Read access, AutoSave will not function.
Admin Checklist to Fix AutoSave Read-Only Issues
Use the following checklist to identify and resolve the cause. Each step targets a specific configuration that can force read-only behavior.
- Check the document library Require Check Out setting
Go to the SharePoint document library that holds the finance workbooks. Click the gear icon and select Library settings. Under General Settings, click Versioning settings. Locate Require Check Out and confirm it is set to No. If it is Yes, change it to No and click OK. This allows multiple users to open and edit the file simultaneously, enabling AutoSave. - Verify user permissions on the library
In the same library settings, click Permissions for this document library. Select the finance group or user and check their permission level. The user must have at least Contribute or Edit to save changes. If they have Read, change the permission level to Contribute. Avoid giving Full Control unless necessary for auditing purposes. - Clear any active file locks
If a user previously opened the workbook and the session did not close, a lock file may remain. Ask the user who last edited the file to close it. Alternatively, as a site collection admin, go to the library, select the file, click the ellipsis (…), and choose Manage checked out files. If any files are listed, force discard the checkout. This releases the lock and allows AutoSave to function. - Check if Known Folder Move is redirecting finance workbooks
In the OneDrive admin center, go to Sync and review the Known Folder Move policy. If the policy redirects Desktop, Documents, or Pictures to OneDrive, and the finance workbook is stored locally, it may be synced to the user’s personal OneDrive instead of the shared SharePoint library. Ensure finance workbooks are saved directly to the SharePoint library path. Move any misdirected files to the correct library using the Move to feature in OneDrive. - Disable any custom script or event receiver that blocks editing
If the library has custom scripts or event receivers that enforce read-only state based on metadata, they can interfere with AutoSave. In the SharePoint admin center, go to Settings and check if Custom Script is enabled for user sites. If it is, consider disabling it for the site collection hosting the finance library. Test by opening a workbook after disabling custom scripts. - Confirm that the file is not marked as Final or Read-Only in Word
Open the workbook in Word. Go to File > Info and check if the Mark as Final button is highlighted. If it is, click it to unmark. Also check if the file has a password or is restricted by Information Rights Management. Remove any such restrictions from the file properties in the library.
If AutoSave Still Opens Read-Only After the Main Fix
Some issues persist even after applying the checklist. The following scenarios are common for finance workbooks and require additional steps.
OneDrive Sync Shows a Red X on Finance Workbooks
A red X indicates a sync conflict. Open the OneDrive activity center, click the red X, and review the error. Common causes include file name conflicts or blocked file types. Rename the file to remove special characters. If the file type is blocked, go to the OneDrive admin center > Sync > File protection and allow the .docx extension. After resolving, right-click the file in File Explorer and select Sync to force a resync.
AutoSave is Grayed Out Even With Correct Permissions
This occurs when the file is stored in a location that OneDrive does not recognize as a synced library. Verify that the file path starts with the OneDrive folder or the SharePoint Documents folder. If the file is on a network drive or local desktop, move it to the synced OneDrive folder. Use the Move to feature in OneDrive.com to transfer the file to the correct library. After moving, open the file from the new location and AutoSave should become active.
Finance Workbooks Open in Protected View
Protected View opens files from the internet as read-only. If the workbook is downloaded from an email or an external link, Word treats it as unsafe. Save the file to the OneDrive or SharePoint library before opening. In Word, go to File > Options > Trust Center > Trust Center Settings > Protected View and uncheck Enable Protected View for files originating from the internet. This should be done only for trusted finance workbooks.
| Item | Require Check Out Enabled | Require Check Out Disabled |
|---|---|---|
| Description | Only one user can edit at a time; others see read-only | Multiple users can co-author; AutoSave works for all editors |
| AutoSave behavior | Disabled for all users except the checkout holder | Enabled for all users with Contribute or Edit permissions |
| Best for finance workbooks | When strict version control is required and co-authoring is not needed | When teams need real-time collaboration and automatic saving |
After completing the checklist, finance team members can open workbooks with AutoSave active. The next time a user opens a workbook, they should see AutoSave enabled in the title bar. For ongoing management, review the document library settings quarterly to ensure they match the team’s collaboration needs. A practical tip: use SharePoint retention labels to protect finance data instead of Require Check Out, because labels preserve AutoSave functionality while still preventing accidental deletion.