Issue with Folder Permissions After SharePoint Migration
Hello
Please i need your help on this issue.
We are currently facing an issue with the permissions of our folders after migrating our data to SharePoint. Specifically, we have discovered that our subfolders were shared separately and that the inheritance has been removed locally.
For example, consider the following structure:
– **Folder A:**
– Folder A1
– Folder A1.1
In this structure, if Folder A1.1 is shared with user1, user1 does not have access to Folder A and Folder A1. As a result, user1 cannot access or see Folder A1.1 without being granted access to both Folder A and Folder A1.
To grant user1 access to Folder A1.1, I would have to:
1. Add user1 as a reader to Folder A.
2. Manually remove user1 from all subfolders under Folder A except for Folder A1.1.
We are facing this issue with multiple subfolders and do not have a comprehensive list of subfolders that were shared separately. Additionally, there are many unique permissions involved.
What is the best approach to resolve this issue?
Hello Please i need your help on this issue. We are currently facing an issue with the permissions of our folders after migrating our data to SharePoint. Specifically, we have discovered that our subfolders were shared separately and that the inheritance has been removed locally. For example, consider the following structure:- **Folder A:** – Folder A1 – Folder A1.1 In this structure, if Folder A1.1 is shared with user1, user1 does not have access to Folder A and Folder A1. As a result, user1 cannot access or see Folder A1.1 without being granted access to both Folder A and Folder A1. To grant user1 access to Folder A1.1, I would have to:1. Add user1 as a reader to Folder A.2. Manually remove user1 from all subfolders under Folder A except for Folder A1.1. We are facing this issue with multiple subfolders and do not have a comprehensive list of subfolders that were shared separately. Additionally, there are many unique permissions involved. What is the best approach to resolve this issue? Read More