Forum Discussion
Hero and Quick Links web parts not supporting library and folder links
In the last few days, I noticed the "picker" modal used by the Hero and Quick Links visually changed. I didn't think anything of it at first until I realized the Hero web part was no longer allowing me to select libraries or folders to serve as the link. This was using the "Site" blade, which appropriately shows all the libraries and lets me drill into each and see the contents, but the ability to select a library or folder doesn't work. To make matters much worse, the "From a link" blade doesn't work either. "From a link" now seems to have a new validation component, so when I attempt to paste in a library or folder URL (i.e. https://tenant.sharepoint.com/sites/HR/Benefits) it detects that it's a SharePoint resource and displays a folder for me to select before I'm allowed to commit it - problem is, I still can't select this. I've tried pointing to the .aspx page that correlates to a library/folder view - doesn't work. I tried creating a Link in the library/folder that points to itself - I can't select these either.
The Quick Links web part, on the other hand, does allow me to select these - same exact UI but allows for selecting libraries and folders. This does work for folders, but does not work for libraries. It visually looks like it works for libraries, but when you save the change is not really committed.
I'm genuinely surprised to not have found this issue reported elsewhere so far. I assume this has to be a bug and hope it's fixed soon - allowing your most popular web parts to link to the root of content in your own platform is one of the most basic feature requirements and for this to break and not be noticed is pretty alarming.
6 Replies
- Jordan_PowerCopper Contributor
M$ Support responded to my ticket earlier in the week. I repo'd the issue for them and they said they'd refer it to the team. Yesterday, they sent me an email stating it was still under review.
This morning, in a Reddit thread -
https://www.reddit.com/r/sharepoint/comments/1rffw52/cant_add_document_libraries_to_quick_links_or/ -
related to this issue, someone posted a potential workaround using the "?web=1" query string parameter using "From a link". Excitedly, I went to test it out when suddenly, my modal pickers have reverted back to their previous iteration, meaning "From a link" works as it did before. I don't know if our tenant had our UI changes rolled back as part of my support case, or what's going on, but hopefully that workaround will help anyone still suffering from this issue.
- castoCopper Contributor
I'm having the same issue. I'm also noticing that a folder that I had previously linked to in a Hero webpart is no longer working. I'm really hoping this is a just a bug they can fix asap and not an intentional update.
- stillwatergirlCopper Contributor
I just figured out that if I use the hero web part in the carousel view, the link functionality doesn't work. I made a copy of the same web part and selected tile view and the links were all there and functioned properly. That said, I know I've used this web part on other pages and haven't had the link issue before. Has something changed?
- TheAndyIron Contributor
I raised a support case about this exact same issue for our tenenat on 19 Feb 2026 with screen recording and .har network trace pending an upload link from them but and have had zero response from Microsoft Support to date. Have been attempting to escalate this through our Microsoft Account Management.
- MKBTCopper Contributor
Has anyone seen or received any updates on this one as yet? As of yesterday, our team is unable to add library links to either Hero or Quick links webparts. I have tried every combination of recommendations I have seen provided - but nothing is working and it is causing great frustration and delays to our teams. Any updates as to when this may be resolved would be much appreciated.
- TheAndyIron Contributor
As of this morning it's working correctly now in our tenant using both the 'From a link' and via the new ability to select 'Site' then by directly selecting the required document library. Nice one! Glad it's fixed, but perhaps some additional testing needed for next time before rolling into production ;)