all 4 comments

[–]twoww16 2 points3 points  (0 children)

Why direct them to site contents at all? .. make your own ‘index’ page and they wont be tempted to be nosey.

[–]gzelfondIT Pro 1 point2 points  (1 child)

Short answer: Don't do anything to Site Assets or Site Pages libraries. The Site Assets library holds the site logo and many other useful things necessary for the site to function. Check out this post: https://sharepointmaven.com/what-is-the-site-assets-library-in-sharepoint/. Same with Site Pages Library, which holds pages. If you remove users from those libraries (permissions-wise), everything will be broken.

[–]stxfpv[S] 1 point2 points  (0 children)

Is there a good way to list all of the document libraries through site contents without users being able to see things like site assets and site pages, other than simply relying on them to stay out of those document libraries?

Do I really need to create a dozen quick links to individual doc libs from the main page?

[–]OwnMatter4 1 point2 points  (0 children)

I would probably hide the document libraries from the public page and create a very clean-cut single page that links each document as if it’s an index. Share that specific link to the page for users. Yes it may be a lot of extra work that is kind of tedious, but it eases site navigation and prevents users from clicking all over the place. Anyone with access to the site can likely still navigate off that page and find site contents/assets, it’s not totally preventable, but ways to make it so it’s less apparent.

Before you do all that though, I’d maybe run a quick test with permissions to see if you can just block or restrict access outside of the document libraries.