Home

Request to Join Private Group

%3CLINGO-SUB%20id%3D%22lingo-sub-165761%22%20slang%3D%22en-US%22%3ERequest%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165761%22%20slang%3D%22en-US%22%3E%3CP%3EWhen%20a%20user%20goes%20to%20SPO%20group%20enabled%20site%20that%20has%20a%20Private%20group%2C%20they%20request%20access%20and%20when%20the%20Group%20Owner%20grants%20access%20(by%20clicking%20on%20the%20link%20in%20the%20email%20they%20opened%20in%20OWA)%20they%20are%20getting%20added%20to%20the%20SP%20Members%20group%20and%20not%20to%20the%20O365%20Group.%20This%20is%20not%20the%20behavior%20that%20we%20are%20expecting%2C%20do%20we%20have%20something%20misconfigured%2C%20or%20is%20this%20the%20way%20it%20supposed%20to%20work%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F64%22%20target%3D%22_blank%22%3E%40Tony%20Redmond%3C%2FA%3E%26nbsp%3BI'm%20reading%20Chpt.%2014%2C%20but%20not%20seeing%20anything%20special%20that%20I%20need%20to%20be%20doing.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EBelow%20is%20the%20invite%20that%20I%20am%20seeing%2C%20clicking%20on%20Accept%20adds%20the%20requester%20to%20the%20SP%20Members%20group%20instead%20of%20the%20expected%20O365%20Group%20as%20a%20member%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F29262iD5804F8315D8100C%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22GroupInvitation.PNG%22%20title%3D%22GroupInvitation.PNG%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-165761%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EGroups%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-365582%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-365582%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20seeing%20the%20same%20behaviour%20on%20a%20bunch%20of%20new%20SharePoint%20sites%20created%20as%20part%20of%20new%20Office%20365%20Groups.%3C%2FP%3E%3CP%3EI%20understand%20that%20from%20SharePoint's%20perspective%2C%20this%20is%20behaving%20as%20designed.%20User%20is%20trying%20to%20access%20a%20SharePoint%20site%20they%20don't%20have%20permission%20to%2C%20SharePoint%20is%20generating%20an%20access%20request%2C%20when%20it's%20approved%20they're%20getting%20added%20to%20the%20SharePoint%20group%2C%20not%20the%20Office%20365%20Group.%20I%20follow%20the%20logic%2C%20but%20it's%20confusing%20for%20end%20users.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20don't%20want%20to%20have%20to%20explain%20to%20a%20collection%20of%20accountants%20and%20actuaries%20the%20difference%20between%20SharePoint%20groups%20and%20O365%20Groups.%20The%20whole%20concept%20of%20Unified%20Groups%2FO365%20Groups%20is%20that%20you%20don't%20grant%20people%20access%20to%20the%20individual%20components%2C%20you%20add%20them%20to%20the%20O365%20Group%20and%20everything%20flows%20from%20there.%20If%20I%20go%20to%20the%20Site%20or%20Document%20Library%20there%20are%20the%20little%20circles%20in%20the%20top%20right%20corner%20showing%20who%20is%20a%20current%20member%20of%20the%20group%2C%20and%20if%20you%20click%20that%20and%20Add%20Member%2C%20the%20person%20gets%20added%20to%20the%20Office%20365%20Group.%20That's%20the%20sort%20of%20behaviour%20I%20expect%20on%20O365-Group-connected%20SharePoint%20Sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMy%20problem%20is%20when%20one%20user%20wants%20access%20to%20some%20files%2C%20and%20another%20user%20emails%20or%20IMs%20them%20the%20link%20to%20the%20sharepoint%20site.%20If%20User1%20is%20already%20in%20the%20Group%2C%20all%20works%2C%20they%20get%20the%20files.%20If%20User1%20isn't%20in%20the%20group%20then%20they%20get%20a%20page%20that%20invites%20them%20to%20generate%20a%20*SharePoint*%20access%20request%2C%20which%20goes%20to%20the%20O365%20Group%20Owner.%20When%20it's%20approved%20they%20get%20access%20to%20the%20SharePoint%20site%2C%20but%20not%20the%20larger%20O356%20Group.%20The%20workflow%20by%20users%20is%20sensible.%20I%20can%20also%20understand%20why%20SharePoint%20currently%20works%20the%20way%20it%20does%2C%20but%20I%20think%20that%20behaviour%20should%20be%20changed%20on%20Group-connected%20sites.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EExplaining%20to%20users%20that%20when%20they%20see%20that%20prompt%20they%20should%20close%20Edge%20and%20go%20to%20*Outlook*%20or%20OWA%20and%20search%20for%20the%20Group%20there%20to%20request%20access...%20people%20aren't%20going%20to%20do%20that.%20It's%20counter-intuitive.%20And%20when%20they%20do%20it%20the%20%22wrong%22%20way%20and%20request%20access%20via%20the%20form%20SharePoint%20puts%20under%20their%20noses%2C%20and%20the%20O365%20Group%20owner%20approves%2C%20they%20*get%20the%20files%20they%20want*%2C%20so%20as%20far%20as%20they're%20concerned%20the%20%22wrong%22%20way%20works%20fine.%20It's%20very%20hard%20to%20train%20people%20to%20do%20something%20totally%20different%20in%20that%20situation.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyway%2C%20that's%20my%20take%20on%20it.%20Rant%20over%20%3D)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-169255%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-169255%22%20slang%3D%22en-US%22%3E%3CP%3EPrivate%20O365%20groups%20are%20listed%20in%20OWA.%20Requesting%20access%20there%20works%20as%20intended.%20Requesting%20access%20via%20the%20link%20to%20the%20team%20site%20associated%20with%20the%20O365%20group%20only%20gives%20users%20access%20to%20the%20team%20site.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165864%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165864%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20think%20that%20might%20have%20been%20the%20case%2C%20but%20I'm%20seeing%20the%20same%20behavior%20in%20a%20clean%20demos.microsoft.com%20site.%26nbsp%3B%20I'm%20wondering%20if%20I'm%20thinking%20about%20this%20wrong%2C%20when%20i%20read%20the%20guidance%20at%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fadd-and-remove-group-members-in-outlook-3b650f4a-5c9b-4f94-a1bb-0cca4b1091de%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2Fadd-and-remove-group-members-in-outlook-3b650f4a-5c9b-4f94-a1bb-0cca4b1091de%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%3C%2FA%3E%20it%20tells%20me%20that%20I%20need%20to%20invite%20someone%20from%20OWA%20to%20join%20a%20Private%20Group.%3C%2FP%3E%0A%3CP%3EDoes%20this%20mean%20that%20if%20I%20just%20tell%20someone%20the%20URL%2C%20then%20they%20cannot%20type%20it%20and%20request%20access%20to%20the%20group%3F%20This%20is%20what%20is%20happening%20and%20I'm%20starting%20to%20think%20that%20this%20scenario%20is%20not%20supported.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165863%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165863%22%20slang%3D%22en-US%22%3EIt%20should%20just%20work%2C%20but%20I%20bet%20you%20have%20found%20an%20edge%20condition%20from%20those%20old%20sites%20and%20their%20messed%20up%20membership%20that%20gets%20in%20the%20way.%20Time%20for%20a%20support%20request.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165862%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165862%22%20slang%3D%22en-US%22%3E%3CP%3EIf%20I%20use%20the%20Admin%20center%2C%20then%20I%20have%20total%20control%20and%20the%20user%20ends%20up%20in%20the%20Office%20Group%20as%20desired.%26nbsp%3B%20But%20I%20don't%20want%20to%20be%20involved%2C%20I'm%20expecting%20the%20management%20of%20Office%20Group%20membership%20to%20be%20handled%20by%20the%20people%20that%20are%20Group%20Owners.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EJuan%20is%20probably%20on%20to%20something%20about%20this%20scenario%20being%20a%20Site%20Access%20Request%20instead%20of%20a%20Group%20Access%20Request%2C%20so%20that%20begs%20the%20question%20of%20how%20does%20a%20user%20request%20access%20to%20an%20Office%20Group%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EMaybe%20I'm%20being%20naive%20or%20dense%2C%20but%20shouldn't%20this%20just%20work%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165847%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165847%22%20slang%3D%22en-US%22%3EBTW%2C%20what%20happens%20if%20you%20add%20the%20user%20to%20the%20group%20with%20PowerShell%2C%20OWA%2C%20or%20the%20Admin%20Center%3F%20I%20wonder%20if%20some%20synchronization%20from%20AAD%20to%20SPODS%20might%20be%20at%20the%20root%20of%20the%20issue.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165846%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165846%22%20slang%3D%22en-US%22%3ESharePoint%20permissions%20are%20complicated.%20I%20don%E2%80%99t%20know%20if%20removing%20everything%20to%20start%20over%20was%20the%20right%20way%20to%20solve%20this%20problem.%20JCM%20has%20much%20more%20experience%20than%20I%20do%20dealing%20with%20the%20juju%20in%20SP%20permissions...%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165816%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165816%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20occurs%20when%20an%20internal%20corporate%20user%20is%20trying%20to%20access%20a%20site%20for%20which%20they%20have%20a%20URL.%20We%20don't%20want%20to%20add%20them%20to%20SP%20Members%20group%2C%20we%20want%20the%20recipient%20of%20the%20request%20(the%20Group%20owner)%20to%20be%20add%20the%20person%20to%20the%20Office%20Group.%20We%20previously%20migrated%20the%20sites%20from%20SP%202010%20and%20made%20them%20into%20Group%20enabled%20team%20sites%20without%20any%20members%20(we%20did%20this%20because%20permissions%20were%20a%20mess%20and%20wanted%20to%20start%20clean).%20Now%20that%20people%20are%20being%20told%20about%20the%20sites%2C%20they%20go%20to%20them%2C%20get%20access%20denied%2C%20request%20access%20and%20end%20up%20in%20the%20SP%20members%20group%20(%3A.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165797%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165797%22%20slang%3D%22en-US%22%3ETo%20me%20this%20functionality%20sounds%20to%20be%20correct%20since%20you%20are%20adding%20the%20user%20to%20the%20SPO%20Site%20and%20not%20the%20Group...Are%20you%20adding%20a%20corporate%20user%20or%20an%20external%20one%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-165796%22%20slang%3D%22en-US%22%3ERe%3A%20Request%20to%20Join%20Private%20Group%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-165796%22%20slang%3D%22en-US%22%3EA%20private%20group%20was%20recently%20set%20up%20in%20our%20organization%20and%20I%20was%20surprised%20to%20receive%20an%20access%20request%20from%20someone%20who%20was%20defined%20as%20a%20Group%20Owner%20in%20Office%20365.%20I%20found%20that%20the%20Office%20365%20Group%20ownership%20permissions%20were%20not%20shown%20in%20the%20SharePoint%20site%20associated%20with%20the%20group.%20I%20feel%20that%20this%20issue%20is%20similar%20to%20the%20one%20being%20described%20here.%3C%2FLINGO-BODY%3E
Dean Gross
Respected Contributor

When a user goes to SPO group enabled site that has a Private group, they request access and when the Group Owner grants access (by clicking on the link in the email they opened in OWA) they are getting added to the SP Members group and not to the O365 Group. This is not the behavior that we are expecting, do we have something misconfigured, or is this the way it supposed to work?

 

@Tony Redmond I'm reading Chpt. 14, but not seeing anything special that I need to be doing.

 

Below is the invite that I am seeing, clicking on Accept adds the requester to the SP Members group instead of the expected O365 Group as a member

GroupInvitation.PNG

 

 

 

10 Replies
A private group was recently set up in our organization and I was surprised to receive an access request from someone who was defined as a Group Owner in Office 365. I found that the Office 365 Group ownership permissions were not shown in the SharePoint site associated with the group. I feel that this issue is similar to the one being described here.
To me this functionality sounds to be correct since you are adding the user to the SPO Site and not the Group...Are you adding a corporate user or an external one?

This occurs when an internal corporate user is trying to access a site for which they have a URL. We don't want to add them to SP Members group, we want the recipient of the request (the Group owner) to be add the person to the Office Group. We previously migrated the sites from SP 2010 and made them into Group enabled team sites without any members (we did this because permissions were a mess and wanted to start clean). Now that people are being told about the sites, they go to them, get access denied, request access and end up in the SP members group (:.

SharePoint permissions are complicated. I don’t know if removing everything to start over was the right way to solve this problem. JCM has much more experience than I do dealing with the juju in SP permissions...
BTW, what happens if you add the user to the group with PowerShell, OWA, or the Admin Center? I wonder if some synchronization from AAD to SPODS might be at the root of the issue.

If I use the Admin center, then I have total control and the user ends up in the Office Group as desired.  But I don't want to be involved, I'm expecting the management of Office Group membership to be handled by the people that are Group Owners.

 

Juan is probably on to something about this scenario being a Site Access Request instead of a Group Access Request, so that begs the question of how does a user request access to an Office Group?

 

Maybe I'm being naive or dense, but shouldn't this just work?

It should just work, but I bet you have found an edge condition from those old sites and their messed up membership that gets in the way. Time for a support request.

I was think that might have been the case, but I'm seeing the same behavior in a clean demos.microsoft.com site.  I'm wondering if I'm thinking about this wrong, when i read the guidance at https://support.office.com/en-us/article/add-and-remove-group-members-in-outlook-3b650f4a-5c9b-4f94-... it tells me that I need to invite someone from OWA to join a Private Group.

Does this mean that if I just tell someone the URL, then they cannot type it and request access to the group? This is what is happening and I'm starting to think that this scenario is not supported.

Private O365 groups are listed in OWA. Requesting access there works as intended. Requesting access via the link to the team site associated with the O365 group only gives users access to the team site. 

We are seeing the same behaviour on a bunch of new SharePoint sites created as part of new Office 365 Groups.

I understand that from SharePoint's perspective, this is behaving as designed. User is trying to access a SharePoint site they don't have permission to, SharePoint is generating an access request, when it's approved they're getting added to the SharePoint group, not the Office 365 Group. I follow the logic, but it's confusing for end users.

 

I don't want to have to explain to a collection of accountants and actuaries the difference between SharePoint groups and O365 Groups. The whole concept of Unified Groups/O365 Groups is that you don't grant people access to the individual components, you add them to the O365 Group and everything flows from there. If I go to the Site or Document Library there are the little circles in the top right corner showing who is a current member of the group, and if you click that and Add Member, the person gets added to the Office 365 Group. That's the sort of behaviour I expect on O365-Group-connected SharePoint Sites.

 

My problem is when one user wants access to some files, and another user emails or IMs them the link to the sharepoint site. If User1 is already in the Group, all works, they get the files. If User1 isn't in the group then they get a page that invites them to generate a *SharePoint* access request, which goes to the O365 Group Owner. When it's approved they get access to the SharePoint site, but not the larger O356 Group. The workflow by users is sensible. I can also understand why SharePoint currently works the way it does, but I think that behaviour should be changed on Group-connected sites.

 

Explaining to users that when they see that prompt they should close Edge and go to *Outlook* or OWA and search for the Group there to request access... people aren't going to do that. It's counter-intuitive. And when they do it the "wrong" way and request access via the form SharePoint puts under their noses, and the O365 Group owner approves, they *get the files they want*, so as far as they're concerned the "wrong" way works fine. It's very hard to train people to do something totally different in that situation.

 

Anyway, that's my take on it. Rant over =)

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
22 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
flashing a white screen while open new tab
cntvertex in Discussions on
13 Replies
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies