Permission & Access Issues

Fix OneDrive Requesting Administrator Rights for SharePoint Shortcuts

John WilsonJohn Wilson Oct 28, 2026 868 views

Question details

Users receive an administrator-rights prompt when trying to rename or delete files through a OneDrive shortcut to a SharePoint library in File Explorer, despite having Full Control permissions.

Fix OneDrive Requesting Administrator Rights for SharePoint Shortcuts
Product
Microsoft OneDrive and SharePoint Online
Device & OS
Windows
Scenario
Managing synced SharePoint documents locally using File Explorer via OneDrive shortcuts.
Observed behavior
An admin-rights requirement symbol is displayed in OneDrive blocking file modification or deletion in File Explorer. The files can still be managed successfully via the SharePoint Online website.
Before you start

Verify that your local Windows account has administrative privileges and confirm that you can still successfully edit, rename, or delete the files directly on the SharePoint Online web interface.

Solution 1Recommended

Migrate Files to a New SharePoint Document Library

Since the synchronization metadata error is often isolated to the original library, creating a new library and moving the files serves as an immediate and reliable workaround.

When an issue impacts multiple users simultaneously but only applies to one specific SharePoint library, the synchronization metadata linking that library to OneDrive may be corrupted. Moving data to a newly created library establishes a fresh sync connection.

1
Create a New Library

Navigate to the same SharePoint site on the web, click 'New', and select 'Document library'. Assign it the same permissions as the original.

2
Transfer the Documents

Select the files or folders in the problematic library and use the 'Move to' function in the top command bar to transfer them to the newly created library.

3
Create a New OneDrive Shortcut

Open the new document library on SharePoint Online, click 'Add shortcut to OneDrive', and verify in File Explorer if the administrator-rights symbol is removed.

Immediate Access: Once the shortcut is recreated from the new library, you should be able to rename and delete files through File Explorer without administrator prompts.
Free Microsoft Office alternative

Experience Hassle-Free Document Management with WPS Office

If complex permission issues and synchronization metadata errors disrupt your workflow, consider using WPS Office. It provides a lightweight, highly compatible, and user-friendly solution for all your daily document needs without the backend hassle.

  1. 1. Download the Installer: Visit the official WPS website and download the free WPS Office installation package.
  2. 2. Install WPS Office: Run the setup file and follow the on-screen instructions for a quick, lightweight installation.
  3. 3. Open and Edit Files: Launch WPS Office to easily open, edit, and save your existing Microsoft Office documents.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formatsLightweight architecture ensures fast loading and smooth performance on WindowsSeamless integration with major third-party cloud storage providersFamiliar user interface makes transitioning quick and easy
microsoft office alternative - wps office

Frequently Asked Questions

Why does OneDrive ask for administrator rights to rename SharePoint files?

This typically occurs due to corrupted synchronization metadata between that specific SharePoint library and the local OneDrive client. The client incorrectly interprets the file ownership or permissions, triggering a false Windows admin prompt.

Can I bypass the administrator prompt if I have Full Control in SharePoint?

No. The issue resides in how the local File Explorer and OneDrive client parse the synced metadata. Even with Full Control on the web interface, the corrupted local sync state will still block modifications.

Will unlinking and relinking my OneDrive fix this issue?

If the issue affects multiple users on the same SharePoint library, unlinking is unlikely to solve it permanently, as the problem is tied to the library's backend metadata rather than a single user's local cache.