Home

Advice about structuring a Sharepoint library / site please and saving as a template

%3CLINGO-SUB%20id%3D%22lingo-sub-1332091%22%20slang%3D%22en-US%22%3EAdvice%20about%20structuring%20a%20Sharepoint%20library%20%2F%20site%20please%20and%20saving%20as%20a%20template%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1332091%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20I%20want%20to%20create%20a%20Team%20site%20which%20relates%20to%20a%20single%20'project'%20with%20a%20large%20amount%20of%20shared%20documents%20which%20will%20cover%20a%20wide%20range%20of%20departments%20who%20all%20contribute%20to%20the%20project.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EEach%20department%20wants%20everyone%20else%20to%20view%20their%20docs%20but%20not%20edit%20or%20delete%20them.%26nbsp%3B%20Some%20departments%20will%20share%20their%20docs%20with%20external%20parties%20such%20as%20contractors.%3C%2FP%3E%3CP%3ECan%20anyone%20comment%20on%20whether%20it%20is%20better%20to%20apply%20permissions%20at%20folder%20level%20within%20a%20single%20doc%20library%20OR%20have%20multiple%20libraries%20within%20the%20site%20and%20apply%20permissions%20at%20library%20level%3F%26nbsp%3B%20What%20are%20the%20advantages%20%2F%20disadvantages%3F%3C%2FP%3E%3CP%3ESecondly%2C%20if%20we%20apply%20permissions%20throughout%20the%20site%2C%20is%20there%20anyway%20of%20saving%20the%20site%20as%20a%20template%20(including%20permissions)%20to%20create%20a%20new%20team%20site%20for%20another%20project%20and%20it%20retain%20all%20the%20settings%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1332091%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDocument%20Library%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESecurity%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESites%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1333385%22%20slang%3D%22en-US%22%3ERe%3A%20Advice%20about%20structuring%20a%20Sharepoint%20library%20%2F%20site%20please%20and%20saving%20as%20a%20template%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1333385%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F612633%22%20target%3D%22_blank%22%3E%40SarahTurner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPersonally%2C%20I%20would%20create%20a%20single%20Communication%20Site%20(as%20I%20have%20found%20this%20to%20be%20the%20best%20of%20the%20new%20modern%20site%20experiences)%2C%20and%20then%20create%20document%20libraries%20for%20each%20individual%20department%2C%20as%20each%20department%20has%20their%20own%20permissions%20and%20sharing%20needs.%20%26nbsp%3BYou%20can%20then%20apply%20permissions%20at%20the%20library%20level.%20%26nbsp%3BI%20think%20this%20will%20work%20better%20for%20you.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20how%20to%20save%20modern%20team%20sites%20as%20a%20template%2C%20take%20a%20look%20at%20this%20previous%20thread.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsharepoint%2Fsave-modern-team-site-as-a-template-amp-provision-using-classic%2Fm-p%2F95307%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsharepoint%2Fsave-modern-team-site-as-a-template-amp-provision-using-classic%2Fm-p%2F95307%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHope%20this%20helps.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1335259%22%20slang%3D%22en-US%22%3ERe%3A%20Advice%20about%20structuring%20a%20Sharepoint%20library%20%2F%20site%20please%20and%20saving%20as%20a%20template%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1335259%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F616707%22%20target%3D%22_blank%22%3E%40PeterRising%3C%2FA%3E%26nbsp%3Bthanks%20for%20your%20response%20-%20out%20of%20interest%2C%20what%20do%20you%20prefer%20about%20the%20communication%20site%20versus%20Team%20site%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1335274%22%20slang%3D%22en-US%22%3ERe%3A%20Advice%20about%20structuring%20a%20Sharepoint%20library%20%2F%20site%20please%20and%20saving%20as%20a%20template%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1335274%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F612633%22%20target%3D%22_blank%22%3E%40SarahTurner%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENothing%20major%2C%20just%20little%20things%20really.%20%26nbsp%3BFor%20example%2C%20(and%20this%20may%20be%20me%20doing%20something%20wrong%20admittedly)%20I%20found%20that%20I%20could%20not%20centre%20a%20single%20column%20web%20part%20on%20a%20team%20site%2C%20whilst%20I%20could%20in%20a%20Communication%20Site.%20%26nbsp%3BI%20also%20found%20that%20on%20a%20Team%20Site%2C%20I%20couldn't%20get%20the%20top%20links%20bar%20working%20as%20well%20as%20in%20a%20Communication%20Site.%20%26nbsp%3BWhat%20I%20tend%20to%20do%2C%20is%20create%20a%20new%20Communication%20Site%2C%20then%20strip%20everything%20out.%20%26nbsp%3BI'll%20add%20a%20hero%20web%20part%20in%20a%20single%20column%20at%20the%20top%2C%20then%20under%20that%20I'll%20have%20the%20news%20feed%20and%20Quick%20links%20in%20a%20Single%20column%20with%20sidebar%20layout.%20%26nbsp%3BI%20think%20this%20looks%20really%20nice.%20%26nbsp%3BLinks%20to%20dept%20doc%20libraries%20can%20be%20tiled%20below%20this%2C%20and%20then%20I'll%20add%20things%20like%20a%20Twitter%20feed%20or%20a%20contacts%20list%20and%20a%20few%20other%20things%20to%20pad%20out%20the%20landing%20page.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

Hi, I want to create a Team site which relates to a single 'project' with a large amount of shared documents which will cover a wide range of departments who all contribute to the project.  

Each department wants everyone else to view their docs but not edit or delete them.  Some departments will share their docs with external parties such as contractors.

Can anyone comment on whether it is better to apply permissions at folder level within a single doc library OR have multiple libraries within the site and apply permissions at library level?  What are the advantages / disadvantages?

Secondly, if we apply permissions throughout the site, is there anyway of saving the site as a template (including permissions) to create a new team site for another project and it retain all the settings?

3 Replies
Highlighted

@SarahTurner 

 

Personally, I would create a single Communication Site (as I have found this to be the best of the new modern site experiences), and then create document libraries for each individual department, as each department has their own permissions and sharing needs.  You can then apply permissions at the library level.  I think this will work better for you.

 

For how to save modern team sites as a template, take a look at this previous thread.  

 

https://techcommunity.microsoft.com/t5/sharepoint/save-modern-team-site-as-a-template-amp-provision-...

 

Hope this helps.

Highlighted

@PeterRising thanks for your response - out of interest, what do you prefer about the communication site versus Team site?

Highlighted

@SarahTurner 

 

Nothing major, just little things really.  For example, (and this may be me doing something wrong admittedly) I found that I could not centre a single column web part on a team site, whilst I could in a Communication Site.  I also found that on a Team Site, I couldn't get the top links bar working as well as in a Communication Site.  What I tend to do, is create a new Communication Site, then strip everything out.  I'll add a hero web part in a single column at the top, then under that I'll have the news feed and Quick links in a Single column with sidebar layout.  I think this looks really nice.  Links to dept doc libraries can be tiled below this, and then I'll add things like a Twitter feed or a contacts list and a few other things to pad out the landing page.