Fix 'Sorry, You Don't Have Access' When Editing SharePoint Group Quick Launch
Question details
The user needs to resolve the 'Sorry, you don't have access' error that prevents editing the SharePoint Online Group Quick Launch, which is commonly caused by disabled custom script settings.
- Product
- SharePoint Online
- Device & OS
- not provided
- Scenario
- A site collection administrator or Owners group member tries to edit the Group Quick Launch on a modern communication site.
- Observed behavior
- SharePoint Online shows 'Sorry, you don't have access' and blocks the edit even for site collection administrators.
Confirm that you have SharePoint admin or global admin permissions for the tenant, and install the latest SharePoint Online Management Shell before running any PowerShell commands.
Enable Custom Script for the SharePoint Site with SharePoint Online Management Shell
Use this when SharePoint blocks Group Quick Launch edits because custom script is disabled; a SharePoint or global admin can allow customizations with one PowerShell command.
The 'Sorry, you don't have access' error on a modern communication site is often caused by the DenyAddAndCustomizePages setting. Enabling custom script through SharePoint Online Management Shell removes this restriction and should take effect immediately.
Install the latest SharePoint Online Management Shell, then open it and sign in with a SharePoint admin or global admin account.
Run Connect-SPOService -Url https://tenant-admin.sharepoint.com and enter your admin credentials when prompted.
Execute Set-SPOSite -Identity https://tenant.sharepoint.com/sites/site-name -DenyAddAndCustomizePages 0, replacing the URL with the affected site address.
Close and reopen the SharePoint site, then try editing the Group Quick Launch again. The change should take effect immediately.
Update the vti_associategroups Property with PnP PowerShell as a Site Collection Administrator
Use this alternative when you are a site collection administrator but cannot enable tenant-level custom script; it sets the Quick Launch group association property directly.
WPS Office: A Free and Familiar Alternative for Microsoft Office and SharePoint Files
For teams that find SharePoint administration and access restrictions heavy, WPS Office offers a free, lightweight Office suite with a familiar ribbon UI, strong Microsoft Office format compatibility, and easy migration for everyday documents.
- 1. Download WPS Office: Go to the official WPS Office website and click Download WPS Office Free, then run the installer.
- 2. Install and launch WPS Office: Complete the installation, open WPS Office, and sign in or continue without an account.
- 3. Open existing Microsoft Office files: Use File > Open in Writer, Spreadsheets, or Presentation to open .docx, .xlsx, and .pptx files and continue working.
Frequently Asked Questions
Why do I get 'Sorry, you don't have access' when editing the SharePoint Group Quick Launch?
The error usually means the SharePoint site has custom script disabled through the DenyAddAndCustomizePages setting. Even site collection administrators can be blocked until a SharePoint or global admin enables custom script.
Do I need global admin permissions to fix the SharePoint Quick Launch access error?
The supported method requires SharePoint admin or global admin permissions to run Set-SPOSite. A site collection administrator may use a PnP PowerShell workaround with the vti_associategroups property.
How long does the Set-SPOSite change take to work?
The change should take effect immediately. If the error still appears, close and reopen the SharePoint site browser session and test the Quick Launch edit again.
Can I enable custom script from the SharePoint user interface instead of PowerShell?
No, SharePoint Online does not provide an equivalent user interface control for this setting. You must use SharePoint Online Management Shell or PnP PowerShell.
Is the PnP PowerShell vti_associategroups method safe?
It directly updates the property bag and can work for site collection administrators, but it may be overwritten by later site customizations. Test in a non-production site first when possible.
