Broad Visitor access OR Use Audience Targeting ? Transparency vs Security

%3CLINGO-SUB%20id%3D%22lingo-sub-1947134%22%20slang%3D%22en-US%22%3EBroad%20Visitor%20access%20OR%20Use%20Audience%20Targeting%20%3F%20Transparency%20vs%20Security%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1947134%22%20slang%3D%22en-US%22%3E%3CP%3EWe've%20got%20a%20fairly%20large%20university%20site%20on%20SPM%2C%20currently%2010%25%20into%20a%20conversion%20off%20of%20SP2013.%3CBR%20%2F%3E%3CBR%20%2F%3EDetermining%20a%20structure%20now...%20I've%20established%20about%2015%20hub%20sites%20(all%20communication%20sites)%2C%20each%20having%203-9%20dept%20sites%20(mix%20of%20Team%20and%20Comm%20sites)%20linked%20into%20that%20hub%20level%20menu.%20We%20utilize%20the%20Start%20page%2C%20as%20well%20as%20a%20Home%20page%20for%20the%20University...where%20there%20is%20a%20menu%20with%20links%20to%20each%20of%20the%20hub%20sites.%3CBR%20%2F%3E%3CBR%20%2F%3EWe%20want%20to%20benefit%20from%20Audience%20Targeting%2C%20but%20are%20torn%20whether%3CBR%20%2F%3E%3CBR%20%2F%3E(A)%20to%20use%20a%20common%20global%20megamenu%20at%20the%20top%20level%20each%20hub%2C%20then%20set%20all%20the%20hubs%20Visitor%20permissions%20to%20'Everyone%20except%20External%20Users'..which%20may%20over-saturate%20the%20Start%20page.%20It%20may%20also%20expose%20(perhaps)%20department%20level%20docs%20to%20outside%20divisions..which%20%3CSTRONG%3Esome%3C%2FSTRONG%3E%20see%20as%20undesirable.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOR%3C%2FP%3E%3CP%3E(B)%20The%20alternative%20is%20to%20remove%20the%20global%20hub%20menu%3B%20give%20users%20access%20to%20ONLY%20their%20depts%20sites%20and%20div%20hubs...and%20rely%20on%20%3CSTRONG%3Eaudience%20targeting%3C%2FSTRONG%3E%20to%20bubble%20up%20documents%20to%20the%20start%20page.%3CBR%20%2F%3E%3CBR%20%2F%3ERemoving%20the%20hub%20navigation%2C%20to%20me%2C%20takes%20away%20the%20desire%20to%20instill%20collaboration%20between%20areas%20of%20the%20university.%20Some%20though%2C%20want%20the%20security%20of%20only%20users%20seeing%20what%20you%20absolutely%26nbsp%3B%3CSTRONG%3Eneed%3C%2FSTRONG%3E%20to%20see.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EWhat%20works%20best%20out%20there%20%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1947134%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esharepoint%20online%20permissions%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
New Contributor

We've got a fairly large university site on SPM, currently 10% into a conversion off of SP2013.

Determining a structure now... I've established about 15 hub sites (all communication sites), each having 3-9 dept sites (mix of Team and Comm sites) linked into that hub level menu. We utilize the Start page, as well as a Home page for the University...where there is a menu with links to each of the hub sites.

We want to benefit from Audience Targeting, but are torn whether

(A) to use a common global megamenu at the top level each hub, then set all the hubs Visitor permissions to 'Everyone except External Users'..which may over-saturate the Start page. It may also expose (perhaps) department level docs to outside divisions..which some see as undesirable.

 

OR

(B) The alternative is to remove the global hub menu; give users access to ONLY their depts sites and div hubs...and rely on audience targeting to bubble up documents to the start page.

Removing the hub navigation, to me, takes away the desire to instill collaboration between areas of the university. Some though, want the security of only users seeing what you absolutely need to see.


What works best out there ?

0 Replies