Oct 29 2019 07:57 AM
Jun 08 2020 09:06 AM
@luvsql I am having a similar issue and will hope someone has an answer :\ I will search and post if I figure something out.
Jun 08 2020 09:38 AM
Hi@luvsql
Thank you for your question.
Do you receive any solution to your question? I wonder about the answer.
Otherwise, you should continue to add a user to a main folder/for all and then remove by one by but this is not an efficient way, I think.
Thank you
Kr
SerayY.
Sep 25 2020 12:47 PM
@luvsql I am having a similar issue. The user can only acces the subfolder using a direct link. They can't see the parent folders. I hope someone find a solution and share it with us.
Sep 25 2020 01:58 PM
Sep 25 2020 02:25 PM
Sep 25 2020 02:49 PM
Sep 25 2020 02:51 PM
Jun 08 2021 04:58 AM
@Constantinismo I have exactly the same requirement. Did you already found an answer to that ?
Thanks
Jan
Jun 08 2021 08:25 PM
Jul 06 2021 12:14 AM
This needs to be fixed. It's a massive security concern having to basically provide a team member access to an entire parent folder then painstakingly remove access to every subfolder you don't want that user to see, not to mention it's extremely time consuming.
I understand SharePoint assigns permissions from the top down through inheritance, but surely it's not hard to provide a base level read-only permission which applies itself ONLY to the parent folders in that particular folder tree when a user is added to a sub-folder, rather than opening up the whole folder tree and hoping you remove the user from any sensitive information before the library syncs with their desktop OneDrive application.
Jul 06 2021 04:59 AM
I would have guessed that if you 'break inheritance' that assigning new permissions to a top folder that they would not trickle down to lower level folders ..... but they do :(
Jul 07 2021 11:04 AM
Apr 04 2022 11:08 AM
May 04 2022 11:26 AM - edited May 04 2022 11:27 AM
This preconfigured permission is available to apply. And it seems like it should do exactly what we are trying to do:
Open - Allows users to open a Web site, list, or folder in order to access items inside that container.
But it doesn't work. I created a test folder in a sub-site library, and tried apply the permission at each level from top down. The user still does not see the parent sites or folders in Navigation.
May 19 2022 10:45 AM
Jun 01 2022 06:00 AM
same problem here! waiting for a feedback
Aug 24 2022 01:00 PM
Jan 26 2023 11:54 PM
I've opened a feedback on the feedback portal for this issue. Everyone please vote for this feature to be implemented by Microsoft:
https://feedbackportal.microsoft.com/feedback/idea/94ac9c78-169e-ed11-a81b-002248519701
Feb 06 2023 06:56 AM