Restrict Permissions for Top Level Folder Only

%3CLINGO-SUB%20id%3D%22lingo-sub-1172334%22%20slang%3D%22en-US%22%3ERestrict%20Permissions%20for%20Top%20Level%20Folder%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1172334%22%20slang%3D%22en-US%22%3E%3CP%3EI'd%20like%20to%20prevent%20users%20from%20creating%20new%20folders%20in%20the%20top%20level%20directory%20of%20a%20SharePoint%20document%20library.%20I%20know%20I%20can%20stop%20inheriting%20permissions%20for%20each%20of%20the%20sub%20folders%20and%20therefore%20have%20different%20permissions%2C%20but%20there%20are%20quite%20a%20lot%20of%20sub-folders%20that%20would%20then%20be%20more%20difficult%20to%20manage.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20a%20simple%20way%20to%20restrict%20folder%20creation%20at%20the%20top%20level%20only%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1172334%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1172419%22%20slang%3D%22en-US%22%3ERe%3A%20Restrict%20Permissions%20for%20Top%20Level%20Folder%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1172419%22%20slang%3D%22en-US%22%3EThere%20is%20a%20setting%20in%20the%20library%20settings%20that%20hides%20the%20create%20folder%20option%20in%20the%20SPO%20UI...but%20if%20the%20users%20sync%20the%20library%20with%20the%20ODFB%20Client%2C%20they%20will%20still%20be%20able%20to%20create%20folders%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1172541%22%20slang%3D%22en-US%22%3ERe%3A%20Restrict%20Permissions%20for%20Top%20Level%20Folder%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1172541%22%20slang%3D%22en-US%22%3EBasically%20there%20is%20no%20easy%20way.%20Even%20if%20you%20could%20or%20use%20the%20method%20Juan%20is%20talking%20about%2C%20you%20would%20prevent%20them%20from%20creating%20folders%20inside%20those%20sub%20folders.%20I%20want%20this%20same%20functionality%20for%20Teams%20attached%20document%20libraries%20%3AP.%20But%20then%2C%20you%20would%20probably%20break%20channel%20creation%20lol.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1173813%22%20slang%3D%22en-US%22%3ERe%3A%20Restrict%20Permissions%20for%20Top%20Level%20Folder%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1173813%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F869%22%20target%3D%22_blank%22%3E%40Chris%20Webb%3C%2FA%3E%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F60%22%20target%3D%22_blank%22%3E%40Juan%20Carlos%20Gonz%C3%A1lez%20Mart%C3%ADn%3C%2FA%3E%26nbsp%3BThanks%20for%20your%20replies.%20Unfortunately%20they%20confirm%20I%20can't%20do%20it%20easily%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2Fimages%2Femoticons%2Fsad_40x40_1.gif%22%20alt%3D%22%3Asad%3A%22%20title%3D%22%3Asad%3A%22%20%2F%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20least%20I%20know%20now!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1606448%22%20slang%3D%22en-US%22%3ERe%3A%20Restrict%20Permissions%20for%20Top%20Level%20Folder%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1606448%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F339060%22%20target%3D%22_blank%22%3E%40jawilson%3C%2FA%3E%26nbsp%3Bcould%20you%20please%20share%20what's%20the%20solution%20here%20that%20you%20were%20confirmed%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3CP%3EThank%20you%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1607532%22%20slang%3D%22en-US%22%3ERe%3A%20Restrict%20Permissions%20for%20Top%20Level%20Folder%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1607532%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F768114%22%20target%3D%22_blank%22%3E%40sarah_mct%3C%2FA%3E%2C%20Unfortunately%20there%20was%20no%20easy%20solution%20for%20my%20problem.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1608462%22%20slang%3D%22en-US%22%3ERe%3A%20Restrict%20Permissions%20for%20Top%20Level%20Folder%20Only%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1608462%22%20slang%3D%22en-US%22%3E%3CP%3EHello%2C%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F339060%22%20target%3D%22_blank%22%3E%40jawilson%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ELet%20me%20make%20sure%20I%20understand%20your%20problem%2C%20correctly%3A%20You%20have%20a%20Document%20Library%20within%20which%20you%20have%20multiple%20sub-folders.%20You%20want%20to%20create%20a%20permission%20setting%20preventing%20users%20from%20creating%20folders%20within%20this%20Document%20Library%20yet%20still%20allow%20them%20to%20create%20folders%20within%20the%20sub-folders.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20this%20is%20a%20correct%20statement%20of%20your%20situation%20have%20you%20considered%20creating%20a%20new%20Permissions%20group%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20the%20top%20level%20(Parent)%2C%20you%20can%20create%20a%20new%20user%20group%20(SiteName)_FolderEditors%20or%20some%20such.%20The%20users%20that%20you%20want%20to%20allow%20to%20create%20sub-folders%20would%20go%20into%20this%20Permission%20Group%20with%20Edit%20rights.%20Those%20same%20users%20would%20be%20removed%20from%20the%20Members%20group%20at%20the%20Parent%20level.%20Refresh%20your%20site%20to%20cascade%26nbsp%3Bthe%20new%20Permission%20Group%20throughout%20your%20site.%20Once%20you%20confirm%20the%20permission%20group%20has%20dispersed%2C%20you%20would%20go%20through%20each%20of%20the%20sub-folders%20and%20break%20the%20Inherit%20Permissions%20link%20at%20the%20top%20level%20of%20each%20of%20those%20folders.%20You%20would%20then%20need%20to%20delete%20the%20new%20Permission%20Group%20you've%20created%20from%20the%20top%20level%2C%20or%20they'd%20still%20have%20Edit%20rights.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAt%20this%20stage%2C%20the%20primary%20Permissions%20Group%3A%20Site%20Owners%2C%20Site%20Members%20%26amp%3B%20Site%20Visitors%20would%20remain%20so%20you%20can%20still%20add%20users%20to%20any%20of%20those%2C%20but%20only%20the%20(SiteName)_FolderEditors%20group%20would%20be%20populated%20and%20have%20the%20rights%20to%20create%20new%20folders%20at%20the%20level%20below%20the%20Parent.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20would%20mean%20that%20if%20you%20need%20to%20add%20members%20broadly%2C%20across%20multiple%20Document%20Libraries%20in%20your%20site%20you%20would%20have%20to%20either%20recreate%20the%20(SiteName)_FolderEditors%20at%20the%20Parent%20level%2C%20and%20return%20to%20Inherit%20Permissions%20across%20the%20board%2C%20or%20go%20through%20each%20of%20the%20Document%20Libraries%20and%20manually%20add%20the%20users%20to%20where%20they%20need%20to%20be.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20matter%20what%20you%20do%2C%20it's%20going%20to%20be%20a%20maintenance%20headache.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I'd like to prevent users from creating new folders in the top level directory of a SharePoint document library. I know I can stop inheriting permissions for each of the sub folders and therefore have different permissions, but there are quite a lot of sub-folders that would then be more difficult to manage. 

 

Is there a simple way to restrict folder creation at the top level only?

6 Replies
There is a setting in the library settings that hides the create folder option in the SPO UI...but if the users sync the library with the ODFB Client, they will still be able to create folders
Basically there is no easy way. Even if you could or use the method Juan is talking about, you would prevent them from creating folders inside those sub folders. I want this same functionality for Teams attached document libraries :P. But then, you would probably break channel creation lol.

@Chris Webb @Juan Carlos González Martín Thanks for your replies. Unfortunately they confirm I can't do it easily :sad:

 

At least I know now!

Hi @jawilson could you please share what's the solution here that you were confirmed :)

Thank you 

@sarah_mct, Unfortunately there was no easy solution for my problem. 

Hello, @jawilson 

 

Let me make sure I understand your problem, correctly: You have a Document Library within which you have multiple sub-folders. You want to create a permission setting preventing users from creating folders within this Document Library yet still allow them to create folders within the sub-folders.

 

If this is a correct statement of your situation have you considered creating a new Permissions group?

 

At the top level (Parent), you can create a new user group (SiteName)_FolderEditors or some such. The users that you want to allow to create sub-folders would go into this Permission Group with Edit rights. Those same users would be removed from the Members group at the Parent level. Refresh your site to cascade the new Permission Group throughout your site. Once you confirm the permission group has dispersed, you would go through each of the sub-folders and break the Inherit Permissions link at the top level of each of those folders. You would then need to delete the new Permission Group you've created from the top level, or they'd still have Edit rights.

 

At this stage, the primary Permissions Group: Site Owners, Site Members & Site Visitors would remain so you can still add users to any of those, but only the (SiteName)_FolderEditors group would be populated and have the rights to create new folders at the level below the Parent. 

 

It would mean that if you need to add members broadly, across multiple Document Libraries in your site you would have to either recreate the (SiteName)_FolderEditors at the Parent level, and return to Inherit Permissions across the board, or go through each of the Document Libraries and manually add the users to where they need to be.

 

No matter what you do, it's going to be a maintenance headache.