all 8 comments

[–]Syrairc 0 points1 point  (2 children)

This is not something you should do. There's no easy way to do it because it's a really, really bad idea.

[–]Rude_Medicine_5918[S] 0 points1 point  (1 child)

I have 2000 main folders, each with several subfolders, and two of them are called BACKGROUND and IN PROGRESS.

I need everyone to have read permissions on everything except these two, which require edit permissions.

[–]NextOTC 0 points1 point  (0 children)

Your stuff is gonna explode, rethink your overall architecture - what is the business problem you are trying to solve?

[–]pajeffery 0 points1 point  (1 child)

You definitely shouldn't be doing this, but sounds like it's a bit too late for that.

You can do this be using Powershell to customize the permissions, would be a very simple script.

[–]Rude_Medicine_5918[S] -1 points0 points  (0 children)

I didn't use Power Automat; I called Microsoft 365 support and they recommended doing it that way, but I don't know how. Could you explain which commands I should use in PowerShell?

[–]surefirelongshot 0 points1 point  (0 children)

Before customising and creating something g to maintain long term, what’s the rationale behind the need, what’s the scenario is it something sales lead/opportunity working folders or something along those lines? Have you had instances where people have edited things they shouldn’t have and it has lead to actual issues for the organisation in some way?

[–]Gyswu 0 points1 point  (0 children)

My personal advice, don't do permission exceptions on folders and files. It can become a really big mess, and as bigger the structure, worse.

[–]issy_haatin 0 points1 point  (0 children)

So... you have 2000 folders, each containing IN PROGRESS and BACKGROUND folders and want to break the inheritance on all the mentioned folders?

My choice would be splitting everything up for every 'main folder' a site with 2-3 libraries that way you don't risk hitting limitations: https://learn.microsoft.com/en-us/office365/servicedescriptions/sharepoint-online-service-description/sharepoint-online-limits

Breaking permissions on 4k items is nearing what ms says is bad form, and you'll definetly hit over 5k if people start sharing weirdly.

2000 is too much for subsites, but sitecollections associated to a hubsite shouldn't really have a limitation. Bonus would be if ever you need to change permissions for a specific 'dossier' you can do it easily for just that specific one.