SharePoint Access Requests Settings

%3CLINGO-SUB%20id%3D%22lingo-sub-190419%22%20slang%3D%22en-US%22%3ESharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190419%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20has%20long%20been%20a%20problem%20but%20there%20appears%20to%20have%20been%20a%20subtle%20but%20significant%20change%20to%20the%20abilities%20here%20in%20SPO.%26nbsp%3B%20It%20appears%20you%20can%20now%20specify%20the%20site%20owners%20group%20as%20the%20destination%20of%20the%20request%20emails.%20%26nbsp%3BHas%20anyone%20seen%20any%20announcements%20or%20tried%20it%20out%20yet%20%3F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20787px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F33561iA1AC21F954270633%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Access%20request%20Settings.png%22%20title%3D%22Access%20request%20Settings.png%22%20%2F%3E%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-190419%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Online%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESites%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-331557%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-331557%22%20slang%3D%22en-US%22%3EThanks%20for%20the%20URL%20-%20saved%20me%20hunting%20high%20and%20low.%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313479%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313479%22%20slang%3D%22en-US%22%3ESorry%20to%20bother%20you%20again%2C%20but%20in%20my%20test%20case%2C%20your%20logic%20does%20not%20work.%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20I%20understand%20your%20logic%2C%20below%20statements%20should%20be%20true%3A%3CBR%20%2F%3E*%20If%20permission%20inheritance%20in%20subsite%20%3D%20TRUE%3B%20then%20requests%20go%20to%20PARENT%20owners%3CBR%20%2F%3E*%20Else%20if%20permission%20inheritance%20in%20subsite%20%3D%20FALSE%3B%20then%20requests%20go%20to%20SUBSITE%20owners%3CBR%20%2F%3E%3CBR%20%2F%3EFor%20my%20case%3B%20the%20logic%20is%20the%20following%3A%3CBR%20%2F%3E*%20If%20Permission%20inheritance%20in%20subsite%20%3D%20TRUE%3B%20then%20requests%20go%20to%20PARENT%20owners%3CBR%20%2F%3E*%20If%20Permission%20inheritance%20in%20subsite%20%3D%20FALSE%3B%20then%20requests%20go%20to%20PARENT%20owners%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20only%20way%20to%20have%20request%20NOT%20go%20to%20parent%20owners%20is%20to%20enter%20an%20email%20address%20in%20the%20second%20option%20in%20the%20settings.%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20would%20be%20great%20if%20the%20first%20option%20had%20a%20drop-down%20menu%20where%20all%20available%20groups%20that%20have%20full%20access%20on%20the%20sub-site%20and%20site%20collection%20was%20listed.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-313188%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-313188%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYes%2C%20the%20mails%20should%20be%20following%20the%20logic%20I%20specified%20above%2C%20not%20the%20string%20(which%20as%20has%20been%20pointed%20out%2C%20doesn't%20actually%20make%20sense%20%3A)%3C%2Fimg%3E%20).%20There%20is%20an%20issue%20with%20the%20logic%20of%20how%20we%20build%20that%20string%20which%20is%20displaying%20the%20wrong%20string%20for%20sub%20sites%20on%20group%20sites.%20We've%20got%20this%20recorded%20and%20will%20look%20at%20fixing%20this%20in%20the%20future.%20Thanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312859%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312859%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F45795%22%20target%3D%22_blank%22%3E%40Andrew%20Silcock%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20both%20for%20your%20considerations.%20The%20subsites%20were%20created%20with%20unique%20permissions%20from%20start.%20I%20should%20mention%20that%20I%20named%20them%20(the%20subsites)%20the%26nbsp%3Babbreviations%20of%20the%20respective%20departments%2C%20for%20instance%26nbsp%3B%22SEC%22%20for%20%22South%20European%20Cluster%22.%20All%20user%20groups%20therefore%20begin%20with%20the%20department%20abbreviation%20(such%20as%20SEC%20Owners%2C%20SEC%20Members%20and%20SEC%20Visitors)%26nbsp%3Bsince%20I%20like%20to%20keep%20things%20short%20and%20sweet.%20After%20creation%20I%20changed%20the%20site%20titles%20manually%20to%20the%20full%20department%20names%20(in%20my%20example%3B%20%3CSPAN%3E%22South%20European%20Cluster%22).%26nbsp%3BNow%20for%20the%20curios%20part%3A%20T%3C%2FSPAN%3Ehe%20user%20group%20referenced%20in%20the%20access%20request%20settings%20is%20%22South%20European%20Cluster%20Admins%22.%20There%20has%20never%20been%20a%20group%20with%20that%20name.%20Does%20this%20information%20reveal%20what%20might%20be%20the%20issue%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312846%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312846%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%26nbsp%3Band%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F3989%22%20target%3D%22_blank%22%3E%40Nicholas%20Byng-Maddick%3C%2FA%3E%2C%20thank%20you%20for%20your%20engagement%20in%20my%20issue.%20All%20of%20the%20subsites%20have%20unique%20permissions.%20I%20have%20tried%20to%20go%20back%20to%20inheriting%20and%20then%20switch%20it%20off%20again%20to%20see%20if%20the%20issue%20would%20be%20solve%2C%20but%20no%20such%20luck.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312806%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312806%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Stephen%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThat's%20likely%20the%20issue%20for%20Gitte%20in%20terms%20of%20the%20access%20requests%20going%20to%20a%20particular%20group.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20shed%20any%20light%20on%20the%20Admin%20group%20though%3F%26nbsp%3B%20Seems%20to%20be%20an%20issue%20with%20sites%20connected%20to%20a%20Hub.%26nbsp%3B%20The%20Access%20request%20settings%20seem%20to%20use%20the%20word%20Admins%20rather%20than%20Owners.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAndy.%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%3CLINGO-SUB%20id%3D%22lingo-sub-312533%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312533%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20can%20shed%20a%20little%20light%20here!%20If%20the%20subsite%20is%20fully%20inheriting%20permissions%20from%20the%20parent%20site%2C%20then%20the%20access%20request%20is%20sent%20to%20the%20parent%20site.%20If%20the%20subsite%20does%20have%20unique%20permissions%2C%20it%20should%20go%20to%20the%20owners%20group%20of%20that%20subsite.%20Hope%20that%20helps!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-312187%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-312187%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20your%20input%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F45795%22%20target%3D%22_blank%22%3E%40Andrew%20Silcock%3C%2FA%3E.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20just%20performed%20a%20simple%20test%3A%26nbsp%3BI%20am%26nbsp%3Ba%20member%20of%26nbsp%3Bboth%20the%20%3CEM%3ESite%20Collection%20Admins%3C%2FEM%3E%20group%20and%20the%26nbsp%3B%3CEM%3ESubsite%20Owners%3C%2FEM%3E%3CSPAN%3E%26nbsp%3Bgroup%3C%2FSPAN%3E.%20First%20I%20removed%20myself%20from%20the%20%3CEM%3ESubsite%20Owners%3C%2FEM%3E%20group%20and%20added%20colleague%26nbsp%3BA%20instead.%26nbsp%3BThen%20I%20had%20colleague%20B%20apply%20for%20accesses%20to%20the%20subsite.%26nbsp%3BIf%20I%20understand%20you%20correcly%2C%26nbsp%3Bthis%20should%20result%20in%20access%20request%20being%20sent%20to%20members%20of%20the%26nbsp%3B%3CEM%3ESubsite%20Owners%3C%2FEM%3E%3CSPAN%3E%26nbsp%3Bgroup%20(in%20my%20test%20case%2C%20to%20colleague%20A).%20However%2C%20in%20my%20test%26nbsp%3Bit%20went%20to%20the%26nbsp%3B%3CEM%3ESite%20Collection%20Admins%3C%2FEM%3E%26nbsp%3Bgroup%20(in%20my%20test%20case%2C%20to%20me).%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20would%20like%20to%20have%20these%20requests%20go%20to%20the%20members%20of%20the%26nbsp%3B%3CEM%3ESubsite%20Owners%3C%2FEM%3E%26nbsp%3Bgroup.%20Perhaps%20there%20should%20be%20a%20functionality%20where%20the%20Site%20Collection%20Admins%20can%20select%20from%20a%20drop-down%20menu%20which%26nbsp%3Bgroup%20should%20receive%20these%20requests.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-310753%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-310753%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Gitte%2FStephen%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20noticed%20this%20today.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20would%20appear%26nbsp%3Bto%20be%20just%20a%20naming%20issue%2C%20as%20access%20requests%20appear%20to%20be%20going%20to%20the%20users%20in%20the%20Owners%20group%2C%20despite%20it%20saying%20%22Site%20Collection%20Admins%22%20under%20the%20site%20access%20request%20settings.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20sites%20are%20recently%20created%20site%20collections%2C%20connected%20to%20O365%20groups%20if%20that%20helps%20diagnostics.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-310281%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-310281%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20a%20situation%20where%20a%20Group%20connected%20site%20is%20the%20parent%20of%20a%20number%20of%20subsites.%20The%20subsites%20are%20in%20themselves%20not%20group%20connected.%20They%20will%20be%20used%20by%20people%26nbsp%3Bgrouped%20into%20MS%20SharePoint%20teams%3A%20%3CEM%3Esubsite%20Owners%3C%2FEM%3E%20and%20%3CEM%3Esubsite%20Members%3C%2FEM%3E.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAccess%20request%20settings%20in%20the%20parent%20is%20as%20expected%2C%20the%20P%3CEM%3Earent%20Admins-group%20%3C%2FEM%3E(i.e.%20O365%20Team%20Owners).%20When%20I%20go%20to%20Access%20request%20settings%20for%20each%20of%20the%20subsites%20however%2C%20the%20name%20of%20the%20suggested%20group%20is%3CEM%3E%26nbsp%3BSubsite%20Admins%3C%2FEM%3E%26nbsp%3Bwhich%20does%20not%20exist%2C%20and%20neither%20does%20a%20corresponding%20O365%20Team.%20How%20can%20I%20make%20access%20requests%20made%20for%20a%20subsites%20go%20to%20the%20subsite's%20Owners%20group%3F%20Below%20image%20shows%20the%20Access%20Request%20Settings%20page.%20Behind%20it%20you%20see%20the%20groups%20available.%20In%20our%20organisation%2C%20the%20name%20of%20any%20O365%20Teams%20group%20starts%20with%20a%20hash%20(%23)%20so%20it%26nbsp%3B%20is%20easy%20to%20identify%20what%20is%20a%20O365%20Teams%20group%20and%20what%20is%20a%20MS%20SharePoint%20Team%20group.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-left%22%20style%3D%22width%3A%20987px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64899i6BE0E6623C994EBF%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22Capture.JPG%22%20title%3D%22Capture.JPG%22%20%2F%3E%3C%2FSPAN%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMuch%20grateful%20for%20any%20assistance%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291895%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291895%22%20slang%3D%22en-US%22%3E%3CP%3EDistribution%20list%20will%20work.%20It%20takes%20any%20email%20address.%20But%20it%20does%20not%20take%20two%20or%20more%20email%20addresses.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-291893%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-291893%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20any%20program%20way%20to%20set%20the%20site%20group%20owners%20to%20receive%20all%20the%20access%20requests%3F%20It%20is%20easy%20to%20do%20in%20the%20browser%2C%20but%20CSOM%2FPowerShell%20cannot%20do%20this.%26nbsp%3BThere%20is%20no%20email%20for%20the%20site%20group%20owners.%26nbsp%3B%3CBR%20%2F%3EThe%20API%20cannot%20accept%20multiple%20email%20addresses%20for%20the%20RequestAccessEmail%2C%20which%20worked%20before%20this%20change.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-276155%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-276155%22%20slang%3D%22en-US%22%3EVoted%2C%20seems%20like%20a%20good%20idea!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-275631%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-275631%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20anyone%20who%26nbsp%3Bis%20able%26nbsp%3Bconfirm%20that%20distribution%20lists%20working%20with%20Request%20For%20Access.%20I've%20got%20an%20error%20when%20I%20try%20to%20put%202%20email%20addresses%20or%20distribution%20list.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3ECheers%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-275605%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-275605%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20problem%20-%20thanks%20so%20much%20for%20letting%20us%20know.%3C%2FP%3E%3CP%3EI've%20added%20a%3CSPAN%3E%26nbsp%3B%3C%2FSPAN%3EUserVoice%20for%20this%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F35766754--request-access-owner-email-add-accept-add-tea%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F35766754--request-access-owner-email-add-accept-add-tea%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-275423%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-275423%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228833%22%20target%3D%22_blank%22%3E%40Dorje%20McKinnon%3C%2FA%3E%20%26amp%3B%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1096%22%20target%3D%22_blank%22%3E%40Dean%20Gross%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20did%20a%20little%20more%20investigating%20with%20the%20featue%20owners%20and%20it%20turns%20out%20I%20was%20100%25%20wrong%2C%20the%20radio%20buttons%20I%20describe%20don't%20actually%20exist%20in%20the%20product%20%3A(%3C%2Fimg%3E%20For%20the%20moment%2C%20the%20best%20thing%20I%20can%20suggest%20is%20to%20submit%20your%20requests%20to%20sharepoint.uservoice.com%20as%20this%20helps%20us%20prioritize%20future%20improvements.%20I've%20also%20passed%20this%20feedback%20along%20directly.%20Thanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-275094%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-275094%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWow%20thanks%20for%20the%20quick%20response.%3C%2FP%3E%3CP%3EFrom%20the%26nbsp%3B%20teams%20app%2C%20users%20can%20search%20for%20teams%2C%20but%20if%20they%20aren't%20a%20member%20of%20it%20already%20they%20get%20the%20%22Hmm%20we%20can't%20find%20any%20matches%22%20message.%3C%2FP%3E%3CP%3EIf%20the%20staff%20member%20gets%20a%20link%20to%20the%20SharePoint%20part%20of%20a%20private%20team%2C%20they%20get%20the%20attached%20standard%20SharePoint%20%22Access%20required%20%3A%26nbsp%3BYou%20need%20permission%20to%20access%20this%20site%22%20message%20with%20a%20comment%20box%20and%20request%20access%20button.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20guess%20is%20that%20there%20is%20a%20setting%20that%20we%20haven't%20set%20in%20our%20tennant%2C%20which%20shows%20the%20radio%20buttons%20you%20mention.%20Just%20like%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1096%22%20target%3D%22_blank%22%3E%40Dean%20Gross%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%5BShout%20out%20for%20Dean%2C%20thanks%20for%20all%20the%20great%20questions%20and%20answers%20you%20post%5D%3C%2FP%3E%3CP%3ELike%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-274887%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-274887%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3Ewe%20are%20not%20seeing%20the%20UI%20you%20describe.%20When%20someone%20navigates%20directly%20to%20a%20SharePoint%20site%2C%20they%20get%20the%20traditional%20Access%20denied%2C%20request%20access%20screen%20and%20then%20the%20SP%20Site%20Owner%20gets%20a%20request%2C%20when%20they%20click%20Accept%2C%20the%20user%20is%20added%20to%20the%20site%20directly%20and%20not%20to%20the%20associated%20O365%20group.%20Attached%20are%20images%20of%20our%20experience.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-274880%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-274880%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F228833%22%20target%3D%22_blank%22%3E%40Dorje%20McKinnon%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20the%20user%20is%20request%20access%2C%20there%20should%20be%20a%20set%20of%20radio%20buttons%20asking%20them%20if%20they%20want%20access%20to%20just%20the%20site%20(or%20file%20or%20folder)%20or%20if%20they%20want%20to%20request%20membership%20in%20the%20group.%20Are%20your%20users%20not%20seeing%20this%3F%20Thanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-272411%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-272411%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20getting%20a%20mismatch%20between%20MS%20Teams%20SharePoint%20Members%20group%20and%20the%20MS%20Teams%20members%20group.%20This%20is%20because%20often%20staff%20have%20their%20first%20interaction%20with%20a%20Team%20via%20the%20Team's%20SharePoint%20site.%20If%20they%20don't%20have%20access%20they%26nbsp%3Brequest%20access.%3C%2FP%3E%3CP%3EThis%20sends%20an%20email%20to%20the%20MS%20Teams%20SharePoint%20Owners%20group%20(the%20default%2C%20and%20how%20our%20sites%20are%20setup)%2C%20the%20owner%20then%20clicks%20the%20Accept%20link%20in%20the%20email.%3C%2FP%3E%3CP%3EAccept%20adds%20the%20person%20to%20the%26nbsp%3B%3CSPAN%3EMS%20Teams%20SharePoint%26nbsp%3BMembers%20group%20BUT%20NOT%20the%26nbsp%3BMS%20Teams%20Members%20group.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20understand%20that%20there%20are%20times%20when%20there%20is%20a%20need%20to%20give%20access%20to%20just%20the%20SharePoint%20content%20%2C%20and%20not%20the%20entire%20Teams%20experience.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20also%20understand%20that%20this%20issue%20is%20arising%20because%20this%20is%20a%20legacy%20feature.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EWhat%20would%20be%20great%20is%20the%20following%3A%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20the%20SharePoint%20site%20is%20related%20to%20a%20MS%20Team%2C%20then%20on%20the%20Permissions%20%2F%20Access%20request%20screen%20have%20a%202%20radio%20buttons%20%22Access%20request%20Accept%20action%3A%20Add%20requester%20to%20SharePoint%20members%20OR%20Add%20requester%20to%20Team%20members%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E-%20The%20other%20way%20to%20do%20this%20would%20be%20in%20the%20Request%20access%20email%20that%20goes%20to%20Site%20owners.%20Change%20the%20wording%20to%20%22Accept%20request%3A%20Add%20to%20SharePoint%20members%20OR%20Add%20to%20Team%20members%22%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ELet%20me%20know%20what%20you%20think%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-251731%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-251731%22%20slang%3D%22en-US%22%3E%3CP%3EIs%20there%20anyone%20who%26nbsp%3Bis%20able%26nbsp%3Bconfirm%20that%20distribution%20list%20is%20work%20with%20Request%20For%20Access.%20I've%20got%20an%20error%20when%20I%20try%20to%20put%202%20email%20addresses%20or%20distribution%20list.%26nbsp%3B%3C%2FP%3E%3CP%3EError%20Sorry%2C%20something%20went%20wrong%3C%2FP%3E%3CDIV%3E%3CDIV%3E%3CDIV%3E%3CDIV%3E%3CDIV%3E%3CSPAN%3EThe%20e-mail%20address%20being%20passed%20is%20either%20empty%2C%20too%20big%20or%20incorrect.%3C%2FSPAN%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-242661%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-242661%22%20slang%3D%22en-US%22%3E%3CP%3EYes%2C%20that%20did%20happen%20to%20us%20and%20is%20causing%20a%20lot%20of%20confusion%20for%20our%20people%20who%20were%20used%20to%20our%20on-premise%20settings--we%20are%20migrating%20to%20the%20Cloud%20and%20everything%20was%20set%20the%20same%20originally%20and%20then%20this%20setting%20showed%20up.%3CBR%20%2F%3E%3CBR%20%2F%3ETo%20workaround%20this%2C%20slowly%20we%20are%20having%20them%20go%20through%20their%20Access%20Request%20Settings%20and%20making%20sure%20they%20are%20correct.%20Although%2C%20the%20individual%20email%20setting%20does%20not%20appear%20to%20be%20working%20as%20expected%20for%20us.%20To%20workaround%20that%2C%20we%20are%20having%20people%20review%20their%20permissions%20and%20making%20sure%20only%20those%20who%20should%20truly%20have%20Owner%20full%20control%20rights%20are%20in%20that%20group.%20A%20lot%20of%20people%20seem%20to%20have%20upwards%20of%2010%20people%20in%20that%20group%20just%20because%20they%20need%20people%20to%20contribute%20to%20the%20site.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-241768%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-241768%22%20slang%3D%22en-US%22%3EIt%20sounds%20like%20the%20Access%20Request%20settings%20needs%20to%20be%20reviewed%20in%20your%20sites.%20It%20also%20sounds%20like%20the%20setting%20has%20been%20switched%20from%20the%20previous%20email%20address%20to%20the%20Owners%20Group%20automagically.%20May%20need%20to%20be%20reset%20back%20manually.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-241757%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-241757%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there.%20Any%20updates%20on%20this%3F%20We%20are%20starting%20to%20receive%20questions%20from%20our%20users%20about%20how%20to%20stop%20the%20Owners%20group%20from%20getting%20the%20requests.%20They%20just%20want%20one%20or%20two%20people%20to%20get%20the%20requests%2C%20not%20the%20whole%20Owners%20group.%20Not%20sure%20how%20to%20stop%20this%20when%20the%20option%20is%20set%20to%20go%20to%20just%20one%20person%20and%20the%20requests%20are%20going%20to%20all%20owners.%20Is%20anyone%20else%20having%20this%20problem%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215268%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215268%22%20slang%3D%22en-US%22%3E%3CP%3EA%20part%20of%20the%20PS%20commands%20are%20not%20yet%20integrated%20into%20CSOM%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20is%20why%20is%20developed%20that%20script%20for%20example%3A%3C%2FP%3E%0A%3CPRE%3E%26lt%3B%23%0ASource%3A%0A%20-%20https%3A%2F%2Fsharepoint.stackexchange.com%2Fquestions%2F219634%2Fsp-online-powershell-web-requestaccessemail-is-not-returning-any-value%0A%20-%20https%3A%2F%2Fsharepoint.stackexchange.com%2Fquestions%2F241415%2Fcsom-property-for-access-request-group%0A%20-%20https%3A%2F%2Fmsdn.microsoft.com%2Fen-us%2Flibrary%2Foffice%2Fmicrosoft.sharepoint.client.web.aspx%0A%20-%20https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FSharePoint-Developer%2FChanging-the-quot-Allow-members-to-share-quot-SharePoint-site%2Ftd-p%2F18562%0A%23%26gt%3B%0A%0A%5Bstring%5D%24MyRootWebURL%20%3D%20%22https%3A%2F%2Ftenant.sharepoint.com%2Fsites%2FYourSiteCollection%22%0A%5Bstring%5D%24SiteOwnerEmailAdress%20%3D%20%22%22%0A%5Bboolean%5D%24ChangeRequestAccessEmail%20%3D%20%24true%0A%0A%5Bstring%5D%24username%20%3D%20%22admin%40tenant.onmicrosoft.com%22%0A%5Bstring%5D%24PwdTXTPath%20%3D%20%22C%3A%5CSECUREDPWD%5CExportedPWD-%24(%24username).txt%22%0A%0A%24secureStringPwd%20%3D%20ConvertTo-SecureString%20-string%20(Get-Content%20%24PwdTXTPath)%0A%24creds%20%3D%20New-Object%20System.Management.Automation.PSCredential%20%24username%2C%20%24secureStringPwd%0A%0Afunction%20Load-DLLandAssemblies%0A%7B%0A%20%5Bstring%5D%24defaultDLLPath%20%3D%20%22%22%0A%0A%20%23%20Load%20assemblies%20to%20PowerShell%20session%20%0A%0A%20%24defaultDLLPath%20%3D%20%22C%3A%5CProgram%20Files%5CSharePoint%20Online%20Management%20Shell%5CMicrosoft.Online.SharePoint.PowerShell%5CMicrosoft.SharePoint.Client.dll%22%0A%20%5BSystem.Reflection.Assembly%5D%3A%3ALoadFile(%24defaultDLLPath)%0A%0A%20%24defaultDLLPath%20%3D%20%22C%3A%5CProgram%20Files%5CSharePoint%20Online%20Management%20Shell%5CMicrosoft.Online.SharePoint.PowerShell%5CMicrosoft.SharePoint.Client.Runtime.dll%22%0A%20%5BSystem.Reflection.Assembly%5D%3A%3ALoadFile(%24defaultDLLPath)%0A%0A%20%24defaultDLLPath%20%3D%20%22C%3A%5CProgram%20Files%5CSharePoint%20Online%20Management%20Shell%5CMicrosoft.Online.SharePoint.PowerShell%5CMicrosoft.Online.SharePoint.Client.Tenant.dll%22%0A%20%5BSystem.Reflection.Assembly%5D%3A%3ALoadFile(%24defaultDLLPath)%0A%7D%0A%0AFunction%20Invoke-LoadMethod()%20%7B%0Aparam(%0A%20%20%20%5BMicrosoft.SharePoint.Client.ClientObject%5D%24Object%20%3D%20%24(throw%20%22Please%20provide%20a%20Client%20Object%22)%2C%0A%20%20%20%5Bstring%5D%24PropertyName%0A)%20%0A%20%20%20%24ctx%20%3D%20%24Object.Context%0A%20%20%20%24load%20%3D%20%5BMicrosoft.SharePoint.Client.ClientContext%5D.GetMethod(%22Load%22)%20%0A%20%20%20%24type%20%3D%20%24Object.GetType()%0A%20%20%20%24clientLoad%20%3D%20%24load.MakeGenericMethod(%24type)%20%0A%0A%0A%20%20%20%24Parameter%20%3D%20%5BSystem.Linq.Expressions.Expression%5D%3A%3AParameter((%24type)%2C%20%24type.Name)%0A%20%20%20%24Expression%20%3D%20%5BSystem.Linq.Expressions.Expression%5D%3A%3ALambda(%0A%20%20%20%20%20%20%20%20%20%20%20%20%5BSystem.Linq.Expressions.Expression%5D%3A%3AConvert(%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%5BSystem.Linq.Expressions.Expression%5D%3A%3APropertyOrField(%24Parameter%2C%24PropertyName)%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%20%5BSystem.Object%5D%0A%20%20%20%20%20%20%20%20%20%20%20%20)%2C%0A%20%20%20%20%20%20%20%20%20%20%20%20%24(%24Parameter)%0A%20%20%20)%0A%20%20%20%24ExpressionArray%20%3D%20%5BSystem.Array%5D%3A%3ACreateInstance(%24Expression.GetType()%2C%201)%0A%20%20%20%24ExpressionArray.SetValue(%24Expression%2C%200)%0A%20%20%20%24clientLoad.Invoke(%24ctx%2C%40(%24Object%2C%24ExpressionArray))%0A%7D%0A%0Afunction%20Get-SPOSubWebs%0A%7B%0A%20Param(%20%0A%20%20%20%20%20%20%20%20%5BMicrosoft.SharePoint.Client.ClientContext%5D%24Context%2C%20%0A%20%20%20%20%20%20%20%20%5BMicrosoft.SharePoint.Client.Web%5D%24RootWeb%20%0A%20%20%20%20)%20%0A%20%0A%20%24Webs%20%3D%20%24RootWeb.Webs%0A%20%24Context.Load(%24Webs)%0A%20%24Context.ExecuteQuery()%0A%20ForEach%20(%24sWeb%20in%20%24Webs)%0A%20%7B%0A%20%20Write-host%20%22%20--------------------------------------------------------%20%22%0A%20%20Write-host%20%22%20%20%20%20%20%20%20--%26gt%3B%26gt%3B%20SubSite%3A%22%2C%20%24sWeb.URL%20-ForegroundColor%20green%0A%20%20Invoke-LoadMethod%20-Object%20%24sWeb%20-PropertyName%20%22HasUniqueRoleAssignments%22%0A%20%20%24context.ExecuteQuery()%0A%20%20Write-Host%20%22%20%20%20%20%20%20%20--%26gt%3B%26gt%3B%20Has%20Unique%20Permissions%3A%22%2C%20%24sWeb.HasUniqueRoleAssignments%0A%0A%20%20if(%24sWeb.HasUniqueRoleAssignments)%0A%20%20%7B%0A%0A%20%20%20Invoke-LoadMethod%20-Object%20%24sWeb%20-PropertyName%20%22RequestAccessEmail%22%0A%20%20%20Invoke-LoadMethod%20-Object%20%24sWeb%20-PropertyName%20%22MembersCanShare%22%0A%20%20%20Invoke-LoadMethod%20-Object%20%24sWeb%20-PropertyName%20%22AssociatedMemberGroup%22%0A%20%20%20Invoke-LoadMethod%20-Object%20%24sWeb%20-PropertyName%20%22AssociatedOwnerGroup%22%0A%20%20%20%24context.ExecuteQuery()%0A%20%20%20Write-Host%20%22%20%20%20%20%20%20%20%20%20%20%20%20--%26gt%3B%26gt%3B%20Request%20Access%20Email%20Before%20change%3A%22%2C%20%24sWeb.RequestAccessEmail%2C%20%22%20-%20Member%20Can%20Share%3A%22%2C%20%24sWeb.MembersCanShare%2C%20%22-%20AssociatedMemberGroup.AllowMembersEditMembership%3A%20%22%20%24sWeb.AssociatedMemberGroup.AllowMembersEditMembership%20-ForegroundColor%20Red%0A%20%20%20Write-Host%20%22%20%20%20%20%20%20%20%20%20%20%20%20--%26gt%3B%26gt%3B%20AssociatedOwnerGroup%20Name%3A%22%2C%20%24sWeb.AssociatedOwnerGroup.Title%20%20%20-ForegroundColor%20Yellow%0A%20%20%20%0A%20%20%20if((%24ChangeRequestAccessEmail)%20-and%20(%24sWeb.RequestAccessEmail%20-ne%20%24SiteOwnerEmailAdress))%0A%20%20%20%7B%0A%20%20%20%20Write-Host%20%22%20%20%20%20%20%20%3D%3D%3D-%26gt%3B%26gt%3B%20Request%20Access%20Email%20to%20change%22%0A%20%20%20%20%24sWeb.RequestAccessEmail%20%3D%20%24SiteOwnerEmailAdress%0A%20%20%20%20%24sWeb.Update()%0A%20%20%20%20%24context.ExecuteQuery()%0A%20%20%20%20Invoke-LoadMethod%20-Object%20%24sWeb%20-PropertyName%20%22RequestAccessEmail%22%0A%20%20%20%20%24context.ExecuteQuery()%0A%20%20%20%20Write-Host%20%22%20%20%20--%26gt%3B%26gt%3B%20Request%20Access%20Email%20After%20change%3A%22%2C%20%24sWeb.RequestAccessEmail%0A%20%20%20%7D%0A%0A%20%20%7D%0A%20%20Get-SPOSubWebs%20-Context%20%24Context%20-RootWeb%20%24sWeb%0A%20%7D%20%0A%7D%0A%0A%0Acls%0AWrite-Host%20%22%20----------------------------------------------%20%22%0ALoad-DLLandAssemblies%0AWrite-Host%20%22%20----------------------------------------------%20%22%0A%0A%20%24Myctx%20%3D%20New-Object%20Microsoft.SharePoint.Client.ClientContext(%24MyRootWebURL)%0A%0A%20%24Myctx.Credentials%20%3D%20New-Object%20Microsoft.SharePoint.Client.SharePointOnlineCredentials(%24creds.UserName%2C%24creds.Password)%0A%20%24Myctx.RequestTimeout%20%3D%201000000%20%23%20milliseconds%0A%20%24MyspoRootweb%20%3D%20%24Myctx.Web%0A%20%24Myctx.Load(%24MyspoRootweb)%0A%20%24Myctx.ExecuteQuery()%0A%0AWrite-Host%20%22%20%22%0AWrite-Host%20%22%20---------------------------------------------------------%22%0AWrite-Host%20%22%20%20%26gt%3B%26gt%3B%26gt%3B%26gt%3B%20%23%20Server%20Version%3A%22%20%24Myctx.ServerVersion%20%22%20%23%20%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%26lt%3B%22%20-ForegroundColor%20Green%20%0AWrite-Host%20%22%20---------------------------------------------------------%22%0AWrite-Host%20%22%20%22%0A%0AWrite-host%20%22%20--------------------------------------------------------%20%22%0AWrite-host%20%22%20%20%20--%26gt%3B%26gt%3B%20RootSite%3A%22%2C%20%24MyspoRootweb.URL%20-ForegroundColor%20green%0A%0AInvoke-LoadMethod%20-Object%20%24MyspoRootweb%20-PropertyName%20%22RequestAccessEmail%22%0AInvoke-LoadMethod%20-Object%20%24MyspoRootweb%20-PropertyName%20%22MembersCanShare%22%0AInvoke-LoadMethod%20-Object%20%24MyspoRootweb%20-PropertyName%20%22AssociatedMemberGroup%22%0AInvoke-LoadMethod%20-Object%20%24MyspoRootweb%20-PropertyName%20%22AssociatedOwnerGroup%22%0A%24Myctx.ExecuteQuery()%0A%0AWrite-Host%20%22%20%20%20--%26gt%3B%26gt%3B%20Request%20Access%20Email%20Before%20change%3A%22%2C%20%24MyspoRootweb.RequestAccessEmail%20-ForegroundColor%20Red%0AWrite-Host%20%22%20%20%20%20%20%20%20%3D%3D%26gt%3B%20Member%20Can%20Share%3A%22%2C%20%24MyspoRootweb.MembersCanShare%0AWrite-Host%20%22%20%20%20%20%20%20%20%3D%3D%26gt%3B%20AssociatedMemberGroup%20Name%3A%22%2C%20%24MyspoRootweb.AssociatedMemberGroup.Title%20%2C%22-%20AssociatedMemberGroup.AllowMembersEditMembership%3A%20%22%20%24MyspoRootweb.AssociatedMemberGroup.AllowMembersEditMembership%20%20-ForegroundColor%20Yellow%0AWrite-Host%20%22%20%20%20%20%20%20%20%3D%3D%26gt%3B%20AssociatedOwnerGroup%20Name%3A%22%2C%20%24MyspoRootweb.AssociatedOwnerGroup.Title%20%20%20-ForegroundColor%20Yellow%0A%0Aif((%24ChangeRequestAccessEmail)%20-and%20(%24MyspoRootweb.RequestAccessEmail%20-ne%20%24SiteOwnerEmailAdress))%0A%7B%0A%20Write-Host%20%22%20%20%20%3D%3D%3D-%26gt%3B%26gt%3B%20Request%20Access%20Email%20to%20change%22%0A%20%24MyspoRootweb.RequestAccessEmail%20%3D%20%24SiteOwnerEmailAdress%0A%20%24MyspoRootweb.Update()%0A%20%24Myctx.ExecuteQuery()%0A%20Invoke-LoadMethod%20-Object%20%24MyspoRootweb%20-PropertyName%20%22RequestAccessEmail%22%0A%20%24Myctx.ExecuteQuery()%0A%20Write-Host%20%22%20%20%20--%26gt%3B%26gt%3B%20Request%20Access%20Email%20After%20change%3A%22%2C%20%24MyspoRootweb.RequestAccessEmail%0A%7D%0A%0AGet-SPOSubWebs%20-Context%20%24Myctx%20-RootWeb%20%24MyspoRootweb%0A%0A%3C%2FPRE%3E%0A%3CP%3EThat%20will%20give%20you%20the%20solution%20to%20manage%20that%20value%20at%20any%20level%20of%20the%20site%20collection.%3C%2FP%3E%0A%3CP%3ETo%20remove%20the%20access%20request%2C%20you%20just%20have%20to%20let%20the%20value%20%22%22%20into%20the%20variable%26nbsp%3B%24SiteOwnerEmailAdress%3C%2FP%3E%0A%3CP%3EIf%20you%20want%20to%20set%20it%20to%20someone%2C%20set%20the%20email%20address.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20adapt%20that%20code%20as%20you%20need.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFab%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-215227%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-215227%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Fabrice%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20the%20same%20issue.%3C%2FP%3E%3CP%3EIn%20case%20the%20option%20is%20%22e-mail%20address%22%20it%20works%20well.%20But%20in%20case%20the%20option%20is%20default%20it%20does%20not%20work.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20983px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F37607iFC423211A5BE9101%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22AccessRequestSetting.png%22%20title%3D%22AccessRequestSetting.png%22%20%2F%3E%3C%2FSPAN%3E%20I%20can%20not%20disable%20the%20%22allowaccess%20requests%22%20in%20case%20option%20is%20default%20via%20PS.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214937%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214937%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20Damien%2C%3C%2FP%3E%0A%3CP%3EIf%20you%20use%20the%20script%20to%20set%20the%20access%20request%20with%20an%20empty%20string%20into%20the%20email%20address%2C%20the%20access%20request%20will%20be%20automatically%20disable.%3C%2FP%3E%0A%3CP%3EFab%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214871%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214871%22%20slang%3D%22en-US%22%3E%3CP%3EI%20also%20like%20the%20change%20but%20I%20have%20a%20question%20which%20I%20have%20asked%20in%20other%20threads%20related%20to%20if%20its%20possible%20to%20disable%20the%20%22allow%20access%20requests%22%20across%20multiple%20sites%20via%20PS.%20I%20can%20see%20there%20are%20commands%20available%20for%20setting%20%22Allow%20members%20to%20share%22%20and%20%22Allow%20members%20to%20invite%22...but%20nothing%20related%20to%20%22Allow%20access%20requests%22.%20Cheers%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214809%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214809%22%20slang%3D%22en-US%22%3E%3CP%3EThanks!%20I%20reset%20the%20Members%20group%20to%20the%20default%20group%20and%20I%20guess%20we'll%20see%20how%20it%20goes%20the%20next%20time%20someone%20requests%20access.%20Keeping%20my%20fingers%20crossed%20that%20this%20fixes%20the%20issue.%20I'm%20pretty%20sure%20that%20someone%20went%20in%20a%20couple%20of%20weeks%20ago%20and%20did%20the%20permsetup%20(that%20Fab%20mentions%20in%20the%20reply)%20on%20the%20site%2C%20and%20wondering%20if%20that%20did%20something%20when%20the%20Owners%20group%20was%20reset.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20site%20was%20a%20collection%20that%20we%20used%20a%20tool%20to%20migrate%20from%20an%20on-premise%20environment%20to%20the%20Cloud%20so%20there%20were%20a%20couple%20of%20permissions%20issues%20we%20found%20that%20needed%20to%20be%20resolved.%20Appreciate%20your%20response!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214798%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214798%22%20slang%3D%22en-US%22%3E%3CP%3EDear%20all%2C%3C%2FP%3E%0A%3CP%3EBe%20careful%20with%20that%20option%2C%20because%20it's%20only%20possible%20for%20the%20%22Members%22%20group.%3C%2FP%3E%0A%3CP%3EIf%20you%20want%20to%20reset%20the%20owners%20and%20visitors%20default%20group%2C%20you%20have%20to%20do%20it%20via%20PowerShell%20or%20via%20this%20technical%20page%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2Ftenant.sharepoint.com%2Fsites%2FyourSite%2FYourSubsite%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2FTenant.sharepoint.com%2Fsites%2FyourSite%2FYourSubsite%2F%3C%2FA%3E%3CSTRONG%3E_layouts%2F15%2Fpermsetup.aspx%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EFab%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214564%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214564%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20fact%20that%20you%20don't%20have%20a%20default%20Members%20group%20is%20never%20a%20good%20sign.%20I%20recommend%20going%20to%20the%20members%20group%20and%20resetting%20it.%20%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20936px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F37467i497CF90589E14890%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22GroupSettings.png%22%20title%3D%22GroupSettings.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214486%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214486%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Tina%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYep%2C%20you%20have%20it%20set%20up%20correctly!%20Let%20me%20see%20what%20I%20can%20dig%20up%20%3A)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214472%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214472%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20quick%20reply.%20I%20am%20attaching%20a%20screen%20shot%20of%20how%20the%20Access%20Request%20setting%20is%20set%20up%20for%20the%20site%20(see%20below).%20When%20someone%20requested%20access%20the%20other%20day%2C%20my%20Team%20Lead%20also%20received%20a%20copy%20of%20the%20email--he%20is%20not%20the%20person%20specified%20below%2C%20but%20he%20is%20in%20the%20Owners%20group.%20I%20just%20cannot%20see%20what%20is%20wrong%20here.%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20666px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F37441i0D264F3B774A934B%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22access%20request%20settings.png%22%20title%3D%22access%20request%20settings.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214463%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214463%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F2925%22%20target%3D%22_blank%22%3E%40Tina%20A%20Garavaglia%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ECan%20you%20share%20how%20you%20have%20the%20access%20requests%20set%20up%3F%20You%20should%20have%20options%20for%20whether%20the%20mails%20go%20to%20the%20owners%20group%20or%20a%20specified%20e-mail%20address.%20If%20they're%20going%20to%20both%2C%20then%20that%20definitely%20doesn't%20sound%20right%20%3A)%3C%2Fimg%3E%20Thanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-214038%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214038%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Stephen%2C%3C%2FP%3E%3CP%3EThis%20change%20was%20a%20surprise%20for%20me%20in%20our%20tenant%3B%20however%2C%26nbsp%3BI%20like%20the%20concept%20of%20now%20being%20able%20to%20assign%20the%20Owners%20group%20or%20an%20individual%20to%20these%20requests%20and%20also%20the%20ability%20to%20set%20a%20custom%20message.%20Nice%20touch.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20question%20%2F%20issue%26nbsp%3Bfor%20me%20is%20why%20when%20we%20set%20an%20email%20address%20to%20receive%20the%20request%2C%20why%20do%20all%20owners%20still%20receive%20the%20access%20request%20email%20and%20not%20just%20the%20email%20address%20specified%3F%20Everything%20looks%20set%20correctly.%20Has%20anyone%20else%20noticed%20this%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-212090%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-212090%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20you%20want%20to%20reset%20that%20default%20groups%20configuration%20(subsite%20or%20rootsite)%20Owners%2C%20Members%2C%20Visitors%20(in%20case%20of%20deletion%20of%20site%20migration%20for%20example).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYou%20can%20use%20that%20technical%20page%20(not%20available%20from%20the%20settings%20menu)%3A%3C%2FP%3E%0A%3CUL%3E%0A%3CLI%3E%3CA%20href%3D%22http%3A%2F%2FTenant.sharepoint.com%2Fsites%2FyourSite%2FYourSubsite%2F%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttp%3A%2F%2FTenant.sharepoint.com%2Fsites%2FyourSite%2FYourSubsite%2F%3C%2FA%3E%3CSTRONG%3E_layouts%2F15%2Fpermsetup.aspx%3C%2FSTRONG%3E%3C%2FLI%3E%0A%3C%2FUL%3E%0A%3CP%3EThat%20will%20offer%20you%20the%20choice%20from%20the%20existing%20groups%20list%20or%20create%20your%20own.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFab%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-211887%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-211887%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Ella%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20might%20have%20deleted%20the%20default%20site%20owners%20group%20from%20site.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%2C%3C%2FP%3E%3CP%3EVijay%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-210803%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-210803%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F160740%22%20target%3D%22_blank%22%3E%40Ella%20Visani%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhat%20type%20of%20site%20are%20you%20on%3F%20Can%20you%20send%20me%20a%20screenshot%20of%20what%20you%20are%20seeing%3F%20Thanks!%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-210722%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-210722%22%20slang%3D%22en-US%22%3E%3CP%3Ehi%20Stephen%3C%2FP%3E%3CP%3Eits%26nbsp%3B%20a%20great%20feature%20but%20today%20I%20came%20upon%20a%20site%20I%20set%20up%20way%20back%20when.%20For%20this%20site%20the%20'group'%20option%20greyed%20out%20and%20says%20'no%20owner%20group%20defined'.%20The%20site%20definitely%20has%20an%20owner%20group.%20any%20ideas%20how%20I%20can%20fix%20this%3F%3C%2FP%3E%3CP%3Ethanks%3C%2FP%3E%3CP%3EElla%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-199823%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-199823%22%20slang%3D%22en-US%22%3EGood%20to%20hear%20Stephen%2C%20looking%20forward%20to%20seeing%20those%20updates!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-199273%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-199273%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F45795%22%20target%3D%22_blank%22%3E%40Andrew%20Silcock%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EYour%20descriptions%20match%20my%20understanding%20as%20well%20%3A)%3C%2Fimg%3E%20We%20don't%20hear%20a%20lot%20of%20feedback%20on%20these%20particular%20strings%20but%20I'll%20keep%20this%20in%20mind%20next%20time%20we%20mess%20with%20the%20page%20(so%20we%20can%20hopefully%20make%20things%20a%20little%20clearer).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EAnd%20I%20would%20love%20to%20see%20access%20requests%20surfaced%20there%20as%20well.%20Nothing%20in%20the%20works%20yet%20but%20definitely%20on%20my%20personal%20wish%20list%20%3B)%3C%2Fimg%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-196625%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-196625%22%20slang%3D%22en-US%22%3EHi%20Stephen%2C%3CBR%20%2F%3E%3CBR%20%2F%3EIt%20would%20be%20great%20to%20see%20access%20requests%20in%20the%20modern%20site%20permissions%20sidebar%2C%20rather%20than%20having%20to%20go%20into%20site%20settings.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-196624%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-196624%22%20slang%3D%22en-US%22%3EThis%20is%20a%20welcomed%20change%2C%20thanks%20Stephen.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20often%20have%20difficulties%20explaining%20the%20top%20two%20access%20request%20settings%20tick%20boxes.%3CBR%20%2F%3E%3CBR%20%2F%3EBelow%20is%20what%20I%20send%20to%20people%2C%20is%20it%20possible%20for%20the%20text%20to%20be%20change%20to%20explain%20things%20a%20bit%20better%3F%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20let%20me%20know%20if%20I%20have%20this%20wrong.%3CBR%20%2F%3E%3CBR%20%2F%3E-------------%3CBR%20%2F%3E*%20Allow%20members%20to%20share%20the%20site%20and%20individual%20files%20and%20folders.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20tick%20box%20determines%20whether%20users%20(ignore%20the%20word%20members%2C%20it's%20misleading%2C%20this%20is%20for%20anyone%20with%20access%20to%20your%20site%20except%20owners)%20can%20share%20the%20site%2C%20files%20and%20folders%20with%20or%20without%20your%20permission%20first.%20If%20this%20is%20unticked%2C%20the%20access%20request%20person%2Fgroup%20will%20receive%20an%20email%20asking%20them%20to%20approve%20every%20time%20someone%20on%20your%20site%20tries%20to%20share%20something.%3CBR%20%2F%3E%3CBR%20%2F%3E*%20Allow%20members%20to%20invite%20others%20to%20the%20site%20members%20group%2C%20*your%20site%20here*%20Members.%20This%20setting%20must%20be%20enabled%20to%20let%20members%20share%20the%20site.%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20tick%20box%20determines%20whether%20users%20(people%20actually%20in%20the%20member's%20group%20this%20time%20or%20with%20similar%20permissions%2C%20but%20not%20people%20in%20the%20visitor's%20group%20or%20with%20similar%20permissions)%20can%20share%20the%20site%20(not%20files%20or%20folders)%20with%20or%20without%20your%20permission%20first.%20If%20this%20is%20unticked%2C%20the%20access%20request%20person%2Fgroup%20will%20receive%20an%20email%20asking%20them%20to%20approve%20every%20time%20people%20in%20the%20member's%20group%20try%20to%20share%20the%20site.%3CBR%20%2F%3E--------------------%3CBR%20%2F%3E%3CBR%20%2F%3EWould%20it%20be%20possible%20to%20alter%20the%20text%20displayed%20to%20make%20things%20clearer%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-195328%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-195328%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1096%22%20target%3D%22_blank%22%3E%40Dean%20Gross%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20the%20user%20is%20requesting%20access%20to%20a%20site%2C%20I%20believe%20that%20option%20does%20exist.%20We%20don't%20offer%20it%20for%20document%20access%20requests%20as%20the%20end%20result%20is%20the%20user%20getting%20access%20to%20additional%20content%20(which%20may%20not%20be%20intended).%20If%20this%20is%20something%20you'd%20like%20to%20see%2C%20feel%20free%20to%20suggest%20it%20on%20User%20Voice%20though!%20Thanks%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-192654%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-192654%22%20slang%3D%22en-US%22%3E%3CP%3EWhat%20I%20really%20would%20like%20to%20see%20it%20that%20these%20requests%20result%20in%20the%20requestors%20account%20being%20added%20to%20the%20Office%20Group%20instead%20of%20the%20SharePoint%20Group.%20Is%20this%20on%20your%20roadmap%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191633%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191633%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F104%22%20target%3D%22_blank%22%3E%40Kevin%20Crossman%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks%20for%20flagging%20this!%20Group%20connected%20sites%20should%20be%20sending%20the%20access%20requests%20to%20the%20O365%20Group%20Admins%20so%20this%20is%20expected.%20The%20other%20two%20are%20anomalies%20so%20we'll%20track%20down%20what's%20happening%20here.%20Thanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191261%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191261%22%20slang%3D%22en-US%22%3E%3CP%3ESome%20anomalies%3A%3C%2FP%3E%0A%3CP%3EIn%20a%20Community%20Site%20(%2Fsites%2F...)%20it%20references%20the%20Owners%20Group.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20a%20Office%20365%20Groups%20connected%20Site%20(%2Fsites%2F...)%20(group%20started%20in%20Yammer)%20it%20references%20the%20%22Admins%22%20group%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIn%20a%20Classic%20Team%20Site%20site%20(%2Fteams%2F...)%20in%20some%20of%20them%20I%20see%20%3CSTRONG%3EMembers%3C%2FSTRONG%3E%20and%20some%20I%20see%20Owners.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-191207%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-191207%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20helped%20make%20this%20improvement%20happen%20so%20if%20you%20have%20any%20questions%2C%20hit%20me%20%3A)%3C%2Fimg%3E%20Message%20center%20post%20may%20have%20expired%20unfortunately%20but%20the%20documentation%20has%20been%20updated.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThere%20were%20two%20pieces%20to%20the%20change%3A%3C%2FP%3E%0A%3CP%3E1)%20Make%20it%20clear%20who%20is%20receiving%20access%20requests%20(especially%20since%20it%20used%20to%20default%20to%20%22someone%40example.com%22%20which%20I'm%20pretty%20sure%20doesn't%20help%20%3B).%20It's%20now%20clear%20if%20you're%20selecting%20the%20default%20(owners)%20or%20another%20e-mail%20address%20of%20your%20choice.%3C%2FP%3E%0A%3CP%3E2)%20Show%20a%20custom%20message%20on%20the%20access%20request%20page.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3EOneDrive%20Program%20Manager%20II%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190514%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190514%22%20slang%3D%22en-US%22%3EYour%20right%2C%20the%20message%20center%20message%20went%20poof%20%3AP.%20I%20concur%20that%20it%20existed%20last%20week%20lol.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190512%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190512%22%20slang%3D%22en-US%22%3EIt's%20a%20much%20needed%20change%2C%20because%20previously%20it%20would%20only%20use%20the%20original%20site%20owner%20it%20seemed.%20or%20it%20was%20random.%20However%2C%20they%20need%20to%20incorporate%20this%20entire%20piece%20in%20with%20guest%20access%20requests%20for%20the%20entire%20group.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20started%20a%20uservoice%20for%20that%20request%20for%20Teams%2C%20but%20it%20encompass%20groups%20in%20general.%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F34054555-microsoft-teams-guest-access-request%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F34054555-microsoft-teams-guest-access-request%3C%2FA%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190444%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190444%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%2C%20it%20looks%20like%20this%20is%20just%20a%20slight%20improvement%20over%20the%20classic%20SP%20site%20access%20request%20process%20and%20will%20still%20result%20in%20requesters%20getting%20added%20to%20the%20SP%20Member%20group%20instead%20of%20to%20the%20connected%20Office%20Group%20(which%20is%20what%20I'm%20still%20hoping%20to%20get)%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190442%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190442%22%20slang%3D%22en-US%22%3E%3CP%3Ethat%20is%20not%20a%20surprise%2C%20the%20inability%20to%20find%20old%20announcements%20in%20the%20Message%20Center%20continues%20to%20be%20a%20disappointment%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190437%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190437%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20the%20first%20option%20is%20configured%2C%26nbsp%3B%3CSPAN%3Eaccess%20requests%20are%20sent%20to%20all%20members%20of%20the%20Team%20Site%20Owners%20group.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIf%20the%20second%20option%20is%20configured%2C%26nbsp%3Baccess%20requests%20are%20sent%20to%20a%20specific%20user%20or%20distribution%20list.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EIn%20any%20case%2C%20%3CSPAN%3Eonly%20members%20of%20the%20Team%20Site%20Owners%20group%20can%20approve%20or%20decline%20access%20requests.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESee%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FSet-up-and-manage-access-requests-94b26e0b-2822-49d4-929a-8455698654b3%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FSet-up-and-manage-access-requests-94b26e0b-2822-49d4-929a-8455698654b3%3C%2FA%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EIMHO%2C%20a%20nice%20addition%20but%20not%20a%20game%20changer...%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190435%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190435%22%20slang%3D%22en-US%22%3EI%20believe%20I%20have%20seen%20this%20in%20a%20message%20posted%20in%20the%20message%20center%2C%20but%20I%20cannot%20find%20it%20now%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-190420%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-190420%22%20slang%3D%22en-US%22%3E%3CP%3EThat%20appears%20to%20be%20wonderful%20news%2C%20but%20is%20it%20going%20to%20the%20SP%20Owners%20group%20members%20OR%20to%20the%20people%20connected%20Office%20Group%20Owner%20role%3F%3C%2FP%3E%3CP%3EAny%20idea%20if%20there%20is%20any%20powershell%2Fcsom%20cmd%20to%20implement%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-667632%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-667632%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20there%20any%20updates%20regarding%20a%20CSOM%20endpoint%20to%20set%20this%20setting%20to%20OwnerGroup%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20hundreds%20of%20site%20collections%20which%20are%20still%20set%20to%20the%20email%20adress%20but%20we%20do%20not%20want%20to%20manually%20set%20them%20to%20the%20OwnerGroup%20setting.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-667648%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-667648%22%20slang%3D%22en-US%22%3EThis%20is%20also%20available%20in%20CSOM%20for%20quite%20some%20time%20but%20was%20not%20really%20documented.%3CBR%20%2F%3E%3CBR%20%2F%3EYou%20can%20reset%20the%20setting%20to%20OwnerGroup%20by%20using%3A%3CBR%20%2F%3E%3CBR%20%2F%3Econtext.Site.RootWeb.SetUseAccessRequestDefaultAndUpdate(true)%3B%3CBR%20%2F%3Econtext.Site.RootWeb.Update()%3B%3CBR%20%2F%3Econtext.ExecuteQuery()%3B%3CBR%20%2F%3E%3CBR%20%2F%3EIf%20the%20settings%20is%20different%20for%20subwebs%20you%20have%20to%20reset%20it%20too.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856327%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856327%22%20slang%3D%22en-US%22%3EHello%2C%20I%20am%20facing%20the%20same%20issues%20.%3CBR%20%2F%3EThe%20request%20goes%20to%20the%20site%20collection%20admin%20not%20the%20group%20owners.%3CBR%20%2F%3EPermission%20has%20been%20broken%20from%20the%20Parents%20site%20.%3CBR%20%2F%3EAny%20clue%20what%20I%20can%20do%20%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856363%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856363%22%20slang%3D%22en-US%22%3EGo%20to%20the%20Site%20Settings%2C%20Permission%2C%20Advanced%20Permission%2C%20Allow%20Request%20Settings%20page%20and%20reset%20it%20to%20the%20Group%20Owners%20option%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-867603%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-867603%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%26nbsp%3BI%20have%20TEAMS-enabled%20modern%20team%20sites%20and%20I%20would%20like%20the%20Owners%20group%20to%20receive%20the%20request%20for%20access%20emails.%20It%20appears%20to%20be%20hard-coded%2C%20if%20you%20will%2C%20to%20the%20%22Admins%22%20which%20I%20am%20assuming%20are%20the%20site%20collection%20admins.%20This%20role%20is%2C%20virtually%2C%20obsolete%20in%20modern%2C%20flat%20architecture%20unless%20there's%20something%20I'm%20overlooking.%20How%20do%20I%20get%20my%20modern%20sites%20to%20reference%20the%20Owners%20perm%20group%20instead%20of%20the%20collection%20admins%3F%26nbsp%3B%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-868059%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-868059%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F11513%22%20target%3D%22_blank%22%3E%40Lisa%20Stebbins%3C%2FA%3E%2C%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20Group-connected%20sites%2C%20the%20hard-coded%20option%20should%20send%20the%20access%20requests%20to%20all%20the%20Group%20administrators%20(which%20may%20or%20may%20not%20be%20the%20same%20as%20the%20site%20administrators%20or%20site%20owners).%20If%20the%20default%20isn't%20working%2C%20the%20best%20option%20unfortunately%20is%20to%20create%20a%20DL%20of%20the%20site%20owners%20%26amp%3B%20enter%20that%20into%20the%20e-mail%20address%20field.%20Thanks!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EStephen%20Rice%3C%2FP%3E%0A%3CP%3ESeniorProgram%20Manager%2C%20ONeDrive%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-868256%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-868256%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3EThank%20you%20for%20a%20quick%20response.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20found%20that%2C%20with%20sites%20connected%20to%20a%20Hub%2C%20the%20'admin'%20is%20the%20site%20collection%20admins%20for%20the%20%3CSTRONG%3Ehub%3C%2FSTRONG%3E%20site%2C%20which%20is%20completely%20wrong%20if%20the%20idea%20is%20to%20delegate%20that%20kind%20of%20task%20to%20the%20individual%20site's%20owners.%20And%2C%20for%20those%20not%20connected%20to%20a%20hub%2C%20collection%20admin%20can%20be%20the%20same%2C%20different%20or%20include%20other%20users%20who%20are%20not%20members%20of%20TEAMS%20and%20the%20associated%20website%20so%20they%20don't%20want%2C%20nor%20should%20they%20get%20the%20access%20request%20notifications%20that%20can't%20process.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUnfortunately%2C%20manually%20creating%20distribution%20list%20for%20every%20TEAM%20that%20users%20create%20isn't%20a%20scalable%20workaround.%20Any%20other%20ideas%3F%20To%20me%2C%20it%20just%20needs%20to%20offer%20a%20choice%20rather%20than%20be%20hard-coded%20to%20the%20one.%20Allow%20us%20to%20choose%20Admins%20or%20the%20site's%20Owners%20and%20it%20would%20solve%20all%20of%20this%2C%20don't%20you%20think%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBy%20the%20way%2C%20what%26nbsp%3B%3CEM%3Eis%20%3C%2FEM%3Ethe%20purpose%20of%20the%20site%20collection%20administrator%20in%20contrast%20to%20the%20site%20Owners%20now%20that%20there%20is%20only%20one%20site%20per%20site%20collection%3F%20Maybe%20that's%20where%20my%20disconnect%20is%3A%20I'm%20not%20understanding%20the%20role's%20'raison%20d'etre'%20in%20the%20Modern%20configuration%20and%20architecture.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20again%20for%20a%20quick%20answer.%20Really%20appreciate%20that.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870239%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870239%22%20slang%3D%22en-US%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181%22%20target%3D%22_blank%22%3E%40Stephen%20Rice%3C%2FA%3E%2C%3CBR%20%2F%3EThis%20may%20be%20a%20disconnect%20for%20me%3A%20when%20I%20look%20at%20the%20groups%20(which%20is%20via%20TEAMS)%2C%20I%20don't%20see%20a%20'Group%20administrators'%20role%20as%20you%20mentioned.%20All%20I%20see%20are%20the%20TEAM's%20Owners%20and%20Members.%20Where%20can%20I%20find%20the%20additional%20group's%20administrators%20listed%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-870260%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-870260%22%20slang%3D%22en-US%22%3Eyou%20need%20to%20open%20the%20SharePoint%20site%20that%20is%20associated%20with%20your%20Team%20to%20see%20these%20settings.%3CBR%20%2F%3E%3CBR%20%2F%3EOpen%20the%20SPO%20Site%2C%20click%20the%20Settings%20Gear%20for%20the%20site%20(between%20the%20Bell%20and%20the%20%3F)%20then%20choose%20Site%20Permissions%20this%20will%20take%20you%20to%20the%20SharePoint%20permission%20page%20that%20provides%20sharepoint%20specific%20capabilities.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-874970%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-874970%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F1096%22%20target%3D%22_blank%22%3E%40Dean%20Gross%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20checked%20that%2C%20however%2C%20I'm%20under%20the%20impression%20that%20Site%20Collection%20Admins%20and%20the%20%22Admins%22%20designated%20in%20the%20Access%20Request%20settings%20when%20the%20site%20is%20teamified%2C%20are%20different%20since%2C%20when%20the%20site%20is%20not%20teamified%2C%20the%20reference%20is%20to%20Owners%2C%20not%20Admins.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20are%20you%20saying%20that%20the%20teamified%20site's%20reference%20to%20'Admins'%20in%20the%20Access%20Request%20Settings%20is%2C%20actually%2C%20the%20Site%20Collection%20Admins%3F%20If%20so%2C%20this%20becomes%20a%20problem%2C%20I%20believe%2C%20when%20the%20site%20is%20associated%20with%20a%20Hub%20because%20then%2C%20the%20Site%20Collection%20Admins%20that%20receive%20the%20requests%20for%20access%20are%20those%20of%20the%20hub%20site%20instead%20of%20the%20site%20itself.%20In%20the%20delegated%20world%20of%20one-site-per-site-collection%20that%20we%20live%20in%20now%2C%20the%20site%20owners%20need%20to%20be%20getting%20the%20requests%2C%20not%20the%20Collection%20Admins%2C%20and%20to%20set%20up%20a%20separate%20DL%20for%20each%20site%2C%20as%20a%20workaround%2C%20does%20not%20promote%20self-management%20or%20delegation%20or%20get%20IT%20out%20of%20the%20middle%20of%20it.%20For%20us%20anyway%2C%20it%20creates%20the%20very%20bottleneck%20we're%20trying%20to%20eliminated%20by%20using%20Modern%20sites%2C%20hubs%2C%20and%20group%20functionality.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWould%20you%20please%20clarify%20this%20for%20me%3F%20Thanks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-875032%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-875032%22%20slang%3D%22en-US%22%3EWhen%20a%20SPO%20site%20is%20Group%20enabled%2C%20the%20accounts%20that%20are%20assigned%20to%20the%20Owner%20role%20within%20the%20associated%20Office%2FAAD%20group%20become%20SCAs%20due%20to%20the%20fact%20that%20the%20Office%20group%20is%20assigned%20to%20the%20SCA%20role%20in%20SPO.%20While%20the%20entire%20group%20is%20assigned%20to%20the%20SCA%20role%2C%20their%20is%20some%20code%20running%20in%20the%20background%20that%20prevents%20the%20Members%20of%20the%20group%20from%20performing%20tasks%20that%20should%20only%20be%20done%20by%20the%20SCA.%3CBR%20%2F%3EAssociating%20a%20site%20to%20a%20Hub%20does%20not%20affect%20security.%20This%20can%20become%20a%20problem%20if%20the%20Hub%20Site%20owner%20does%20not%20have%20access%20to%20a%20linked%20site.%20This%20needs%20to%20be%20manually%20coordinated.%3CBR%20%2F%3Ein%20this%20approach%20Group%20Owners%20are%20also%20Site%20Owner%20as%20well%20as%20SCAs%2C%20which%20demonstrates%20the%20need%20to%20have%20a%20good%20Group%20Management%20strategy.%20Groups%20can%20easily%20get%20orphaned%20when%20a%20single%20owner%20leaves%20and%20the%20only%20way%20to%20prevent%20this%20is%20to%20have%20some%20custom%20scripts%20running.%3CBR%20%2F%3EDon't%20create%20separate%20DLs%2C%20that%20will%20just%20make%20things%20more%20confusing%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-881222%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-881222%22%20slang%3D%22en-US%22%3EThank%20you%20for%20the%20reply%20.%3CBR%20%2F%3EI%20discovered%20that%20for%20a%20subsite%20with%20project%20template%20by%20design%20the%20access%20request%20goes%20to%20the%20site%20collection%20administrator%20except%20I%20specify%20the%20email%20address%20directly.%3CBR%20%2F%3E%3CBR%20%2F%3EThanks%20!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-882190%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-882190%22%20slang%3D%22en-US%22%3E%3CP%3E%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%3B%20It%20is%20still%20available%20in%20Message%20Center%20with%20%3CSTRONG%3EID%20%3D%20MC189888%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMessage%20Center%20Link%3A%26nbsp%3B%3CA%20title%3D%22Site%20owners%20can%20now%20manage%20sharing%20and%20access%20request%20settings%20from%20the%20Site%20permissions%20panel%22%20href%3D%22https%3A%2F%2Fadmin.microsoft.com%2FAdminPortal%2Fhome%3Fswitchtomodern%3Dtrue%23%2FMessageCenter%3Fid%3DMC189888%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3ESite%20owners%20can%20now%20manage%20sharing%20and%20access%20request%20settings%20from%20the%20Site%20permissions%20panel%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOffice%20365%20Roadmap%20reference%3A%26nbsp%3B%3CA%20title%3D%22Manage%20sharing%20and%20access%20request%20settings%20from%20the%20Site%20permissions%20panel%22%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-in%2Fmicrosoft-365%2Froadmap%3Frtc%3D1%26amp%3Bsearchterms%3D54983%26amp%3Bfilters%3D%26amp%3Bsearchterms%3D54983%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EManage%20sharing%20and%20access%20request%20settings%20from%20the%20Site%20permissions%20panel%3C%2FA%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-897313%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20Access%20Requests%20Settings%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-897313%22%20slang%3D%22en-US%22%3EThis%20sounds%20like%20just%20what%20I%20have%20been%20asking%20about.%20One%20question%2C%20though%2C%20that%20is%20still%20a%20bit%20of%20a%20gray%20area%20for%20me.%3CBR%20%2F%3E%3CBR%20%2F%3EIn%20this%20new%20feature%2C%20where%20you%20can%20choose%20who%20receives%20the%20access%20requests%2C%20one%20option%20is%20the%20Owners%20which%20sounds%20promising.%20My%20question%20is%2C%20when%20the%20site%20is%20associated%20with%20an%20O365%20Group%2FTEAMS%2C%20does%20that%20option%20actually%20refer%20to%20those%20who%20are%20and%20only%20those%20who%20are%20members%20of%20the%20site's%20owner's%20group%20and%2C%20therefore%2C%20does%20not%20also%20include%20those%20who%20have%20the%20role%20of%20Site%20Collection%20Admin%3F%20I%20ask%20this%20because%2C%20in%20the%20Advanced%20perms%20page%2C%20the%20only%20option%2C%20other%20than%20specific%20email%20address%2C%20was%20%22...Admins%22.%20This%20doesn't%20work%20for%20us%20because%20there%20are%20other%20users%20included%20as%20Site%20Collection%20Admins%20for%20the%20site%20who%20are%20not%20the%20site's%20owners%20and%20should%20not%20be%20receiving%20access%20requests.%20We%20need%20site%20owners%20and%20only%20site%20owners%20to%20receive%20the%20access%20requests%20and%20I'm%20hoping%20that%20this%20new%20features%20is%20meeting%20that%20need.%20Can%20you%20confirm%20one%20way%20or%20the%20other%3F%3C%2FLINGO-BODY%3E
Highlighted
Contributor

This has long been a problem but there appears to have been a subtle but significant change to the abilities here in SPO.  It appears you can now specify the site owners group as the destination of the request emails.  Has anyone seen any announcements or tried it out yet ?

Access request Settings.png 

68 Replies
Highlighted

Hi @Lisa Stebbins,

 

For Group-connected sites, the hard-coded option should send the access requests to all the Group administrators (which may or may not be the same as the site administrators or site owners). If the default isn't working, the best option unfortunately is to create a DL of the site owners & enter that into the e-mail address field. Thanks!

 

Stephen Rice

SeniorProgram Manager, ONeDrive

Highlighted

@Stephen RiceThank you for a quick response.

 

I have found that, with sites connected to a Hub, the 'admin' is the site collection admins for the hub site, which is completely wrong if the idea is to delegate that kind of task to the individual site's owners. And, for those not connected to a hub, collection admin can be the same, different or include other users who are not members of TEAMS and the associated website so they don't want, nor should they get the access request notifications that can't process.

 

Unfortunately, manually creating distribution list for every TEAM that users create isn't a scalable workaround. Any other ideas? To me, it just needs to offer a choice rather than be hard-coded to the one. Allow us to choose Admins or the site's Owners and it would solve all of this, don't you think?

 

By the way, what is the purpose of the site collection administrator in contrast to the site Owners now that there is only one site per site collection? Maybe that's where my disconnect is: I'm not understanding the role's 'raison d'etre' in the Modern configuration and architecture.

 

Thanks again for a quick answer. Really appreciate that.

 

Highlighted
@Stephen Rice,
This may be a disconnect for me: when I look at the groups (which is via TEAMS), I don't see a 'Group administrators' role as you mentioned. All I see are the TEAM's Owners and Members. Where can I find the additional group's administrators listed?
Highlighted
you need to open the SharePoint site that is associated with your Team to see these settings.

Open the SPO Site, click the Settings Gear for the site (between the Bell and the ?) then choose Site Permissions this will take you to the SharePoint permission page that provides sharepoint specific capabilities.
Highlighted

Thanks @Dean Gross 

I have checked that, however, I'm under the impression that Site Collection Admins and the "Admins" designated in the Access Request settings when the site is teamified, are different since, when the site is not teamified, the reference is to Owners, not Admins.

 

So, are you saying that the teamified site's reference to 'Admins' in the Access Request Settings is, actually, the Site Collection Admins? If so, this becomes a problem, I believe, when the site is associated with a Hub because then, the Site Collection Admins that receive the requests for access are those of the hub site instead of the site itself. In the delegated world of one-site-per-site-collection that we live in now, the site owners need to be getting the requests, not the Collection Admins, and to set up a separate DL for each site, as a workaround, does not promote self-management or delegation or get IT out of the middle of it. For us anyway, it creates the very bottleneck we're trying to eliminated by using Modern sites, hubs, and group functionality.

 

Would you please clarify this for me? Thanks.

Highlighted
When a SPO site is Group enabled, the accounts that are assigned to the Owner role within the associated Office/AAD group become SCAs due to the fact that the Office group is assigned to the SCA role in SPO. While the entire group is assigned to the SCA role, their is some code running in the background that prevents the Members of the group from performing tasks that should only be done by the SCA.
Associating a site to a Hub does not affect security. This can become a problem if the Hub Site owner does not have access to a linked site. This needs to be manually coordinated.
in this approach Group Owners are also Site Owner as well as SCAs, which demonstrates the need to have a good Group Management strategy. Groups can easily get orphaned when a single owner leaves and the only way to prevent this is to have some custom scripts running.
Don't create separate DLs, that will just make things more confusing :)
Highlighted
Thank you for the reply .
I discovered that for a subsite with project template by design the access request goes to the site collection administrator except I specify the email address directly.

Thanks !
Highlighted
This sounds like just what I have been asking about. One question, though, that is still a bit of a gray area for me.

In this new feature, where you can choose who receives the access requests, one option is the Owners which sounds promising. My question is, when the site is associated with an O365 Group/TEAMS, does that option actually refer to those who are and only those who are members of the site's owner's group and, therefore, does not also include those who have the role of Site Collection Admin? I ask this because, in the Advanced perms page, the only option, other than specific email address, was "...Admins". This doesn't work for us because there are other users included as Site Collection Admins for the site who are not the site's owners and should not be receiving access requests. We need site owners and only site owners to receive the access requests and I'm hoping that this new features is meeting that need. Can you confirm one way or the other?