Carrying permissions in a site template or a Document Library Template

%3CLINGO-SUB%20id%3D%22lingo-sub-302806%22%20slang%3D%22en-US%22%3ECarrying%20permissions%20in%20a%20site%20template%20or%20a%20Document%20Library%20Template%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-302806%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20creating%20a%20folder%20structure%20that%20requires%20unique%20permissions%20for%2011%20of%20the%20folders%20within%20it.%26nbsp%3B%20The%20structure%20is%20Year%26gt%3BVenue%26gt%3BMonth%26gt%3BEvent%20and%20then%20under%20each%20event%20folder%20is%20where%20we%20will%20have%20the%20same%2011%20folders.%26nbsp%3B%20%26nbsp%3BOnce%20I%20have%20all%20the%20folders%20in%20place%20it%20works%20out%20that%20there%20are%20just%20under%203000%20folders%20in%20total%20depending%20on%20the%20volume%20of%20events%20per%20month.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20want%20to%20be%20able%20to%20set%20the%20permissions%20on%20the%2011%20folders%20and%20then%20be%20able%20to%20copy%20them%20across%20to%20the%20other%20months%20whilst%20retaining%20the%20permissions%20and%20then%20also%20retain%20the%20permissions%20when%20using%20the%20site%20template%20again%20for%20a%20new%20year.%26nbsp%3B%20I%20have%20also%20checked%20to%20see%20if%20this%20is%20possible%20to%20do%20in%20a%20document%20library%20template%20but%20it%20does%20not%20seem%20to%20retain%20the%20security.%26nbsp%3B%20It's%20not%20practical%20to%20set%20the%20permissions%20each%20time%20due%20to%20the%20high%20volume%20of%20folders.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHas%20anyone%20got%20any%20ideas%2C%20suggestions%20or%20workarounds%3F%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-302806%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EPermissions%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-304907%22%20slang%3D%22en-US%22%3ERe%3A%20Carrying%20permissions%20in%20a%20site%20template%20or%20a%20Document%20Library%20Template%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-304907%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20is%20a%20crazy%20amount%20of%20unique%20permissions%20you%20will%20be%20creating%2C%20which%20will%20be%20hard%20to%20manage%20in%20the%20long%20term.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20suggestions%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E1)%20break%26nbsp%3Beach%20of%20the%2011%20folders%20into%20separate%20libraries%20and%20then%20tag%20them%20with%20the%20year%2Fvenue%2Fmonth.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2)%26nbsp%3B%20structure%20it%20in%20a%20way%20where%26nbsp%3Bthe%20permissions%20are%20broken%20at%20the%20library%20level%20only%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

I am creating a folder structure that requires unique permissions for 11 of the folders within it.  The structure is Year>Venue>Month>Event and then under each event folder is where we will have the same 11 folders.   Once I have all the folders in place it works out that there are just under 3000 folders in total depending on the volume of events per month.  

 

I want to be able to set the permissions on the 11 folders and then be able to copy them across to the other months whilst retaining the permissions and then also retain the permissions when using the site template again for a new year.  I have also checked to see if this is possible to do in a document library template but it does not seem to retain the security.  It's not practical to set the permissions each time due to the high volume of folders.

 

Has anyone got any ideas, suggestions or workarounds?  

1 Reply

That is a crazy amount of unique permissions you will be creating, which will be hard to manage in the long term.

 

My suggestions

 

1) break each of the 11 folders into separate libraries and then tag them with the year/venue/month. 

 

2)  structure it in a way where the permissions are broken at the library level only