Remove the "Shared with us" library from showing up in SharePoint Team sites

Nishanth Chakkere Ramesh 400 Reputation points
2024-10-11T09:42:17.68+00:00

Hi,

Is there a way to remove the "Shared with us" library from showing up in SharePoint Team sites.

This library shows up from time to time in the left-hand navigation panel when a SharePoint Team site is accessed. And it does go away after refreshing the site a few times. Is there a more permanent solution to ensure that this library does not show up?

User's image

User's image

Thanks,

Nishanth Chakkere Ramesh

Microsoft 365 and Office | SharePoint | For business | Windows
0 comments No comments
{count} votes

Accepted answer
  1. RaytheonXie_MSFT 40,471 Reputation points Microsoft External Staff
    2024-10-14T01:58:23.3066667+00:00

    Hi @Nishanth Chakkere

    Per my test and research, we are unable to hide the Shared with us by setting currently. Here is a post discussing the similar issue with yours:

    https://techcommunity.microsoft.com/t5/sharepoint/delete-the-quot-shared-with-us-quot-link-on-navigation-menu-for/m-p/840551

    As a workaround, the post mentioned users could inject a css with spfx to custom the navigation bar:

    https://blog.jussipalo.com/2019/09/problem-for-apparently-nearly-3-years.html

    Many features of our current products are designed and upgraded based on customers’ feedback. With requirements like this increase, the problem may well be released in the future. You could vote the request in this link. Thanks for your understanding.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.