We used to make use of shared network drive to share various reports to our staffs. The report administrator will create the nested folder structure and assign permission using CACLS command line tool. Then export various reports to these folders.
The nested folder is like:
Report>DeptA>RegionA>TeamA Report>DeptA>RegionA>TeamB Report>DeptA>RegionB>TeamC Report>DeptB>RegionA>TeamX
All the subfolder have individual permission (broken inheritance). TeamA subfolder can only be read by Team A's members. There are more than 100 teams.
Every month the nested folder structure and the team formation will be changed based on new business need. Team members will be switched to different team. Some staffs will belong to multiple teams.
Although the change is complex, in current setup, the report administrator just need to spend 15 minutes to update his DOS script file and make change using CACLS.
The problem is, we have to replace this share drive setup with SharePoint 2013 Enterprise on-premise. We create a site collection and assign the report administrator as site collection admin. He cannot have PowerShell access. By using SharePoint UI, he can break inheritance of folders and create SharePoint groups for 100+ teams, and then assign permission folder by folder. However it will take him entire day and easily make mistake. Then repeat this painful process every month.
Do you have suggestion to ease his job? I am not looking for identical setup as before. Any method that don't need him repeat same steps 100 times for 100 folders is fine. Also I want to avoid farm solution because I heard it is going to be phased out.
Thank you for any idea!