Home

Bug: A membership change to a private team clears the associated site's Site Visitors access.

%3CLINGO-SUB%20id%3D%22lingo-sub-324588%22%20slang%3D%22en-US%22%3EBug%3A%20A%20membership%20change%20to%20a%20private%20team%20clears%20the%20associated%20site's%20Site%20Visitors%20access.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324588%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20site%20pages%20of%20a%20private%20team%20in%20Teams%20are%20intended%20to%20be%20our%20team's%20public%20interface.%20I%20use%20%22Invite%20People%22%20to%20%22Share%20site%20only%22%2C%20giving%20%22Everyone%20but%20external%20users%22%20Read%20access%20and%20it%20works%20as%20expected.%20However%2C%20%3CSTRONG%3Ewhen%20I%20later%20add%20or%20remove%20a%20team%20member%2C%20within%20a%20few%20minutes%20(5-60)%2C%20the%20Site%20visitors%20access%20is%20cleared%20-%20ouch!%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20tried%20all%20sorts%20of%20paths%20to%20avoid%20the%20problem%2C%20such%20as%20editing%20members%20from%20the%20team%20in%20Teams%2C%20editing%20from%20the%20site%20via%20Add%20Members%2C%20no%20luck.%20I%20tried%20editing%20Site%20visitors%20via%20Invite%20People%20and%20by%20editing%20the%20Site%20Visitors%20group%20directly%2C%20no%20luck%20(problem%20still%20occurs).%20I%20can't%20find%20a%20way%20to%20avoid%20the%20bug%2C%20so%20all%20I%20can%20recommend%20to%20our%20users%20is%20how%20to%20deal%20with%20the%20problem%2C%20knowing%20that%20it%20will%20occur.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWorkaround%2C%20for%20add%2Fremove%20team%20members%3A%3C%2FP%3E%3COL%3E%3CLI%3ERecord%20the%20%22Site%20visitors%22%20information%20for%20the%20site.%3C%2FLI%3E%3CLI%3EAdd%20or%20remove%20team%20members.%3C%2FLI%3E%3CLI%3EWait%20for%20Site%20visitors%20to%20be%20cleared%20(5m%2C%2030m%2C%2060m%3F).%3C%2FLI%3E%3CLI%3ERestore%20%22Site%20visitors%22.%3C%2FLI%3E%3C%2FOL%3E%3CP%3EThis%20workaround%20is%20error%20prone%2C%20in%20that%20users%20will%20likely%20forget%20to%20do%20it%2C%20and%20painful%2C%26nbsp%3Bsince%20they%20may%20not%20remember%20what%20they%20had%20for%20visitor%20access%2C%20so%20can't%20restore%20it%20properly.%3C%2FP%3E%3CP%3E%3CBR%20%2F%3ENote%3A%20I%20can't%20find%20where%20to%20report%20a%20%22bug%22.%20If%20others%20will%20confirm%20this%20is%20a%20bug%20and%20tell%20me%20how%20to%20go%20about%20getting%20Microsoft's%20attention%2C%20I%20will%20appreciate%20the%20help.%3CSTRONG%3E%20If%20you%20try%20to%20reproduce%2C%20don't%20forget%20to%20uncheck%20%22send%20mail%22%20when%20giving%20everyone%20read%20access.%20%3A)%3C%2Fimg%3E%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-324588%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-355981%22%20slang%3D%22en-US%22%3ERe%3A%20Bug%3A%20A%20membership%20change%20to%20a%20private%20team%20clears%20the%20associated%20site's%20Site%20Visitors%20access.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-355981%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20problem%20isn't%20that%20removing%20a%20member%20also%20removes%20them%20from%20the%20associated%20group%2C%20the%20problem%20is%20that%20adding%20or%20removing%20a%20%22member%22%20removes%20%22Everyone%20except%20external%20users%22%20(EEEU)%20from%20Site%20Visitors.%20That%20action%20doesn't%20completely%20clear%20visitors%2C%20it%20leaves%20other%20people%20with%20access%2C%20but%20removes%20EEEU.%20My%20suspicion%20is%20that%20if%20the%20%22member%22%20being%20added%20or%20removed%20is%20in%20a%20group%20in%20Visitors%2C%20that%20group%20is%20removed.%20That%20is%2C%20if%20Bob%20is%20a%20team%20member%20and%20EEEU%20is%20in%20site%20Visitors%20(which%20covers%20everyone%2C%20including%20Bob)%2C%20and%20I%20remove%20Bob%20as%20a%20member%2C%20that%20should%20not%20remove%20EEEU%20from%20Site%20Visitors%20-%20clearly%20a%20bug.%20It%20would%20only%20take%20a%20few%20minutes%20to%20confirm%2C%20but%20it%20would%20be%20nice%20if%20someone%20from%20MS%20would%20confirm%20this%20bug%2C%20properly%20characterize%20it%20and%20provide%20a%20workaround%2C%20if%20there%20is%20one.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325850%22%20slang%3D%22en-US%22%3ERe%3A%20Bug%3A%20A%20membership%20change%20to%20a%20private%20team%20clears%20the%20associated%20site's%20Site%20Visitors%20access.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325850%22%20slang%3D%22en-US%22%3E%3CP%3ESo%20it%20seems%20that%20the%20group%20takes%20over%20control%20of%20the%20standard%20SharePoint%20Group.%3C%2FP%3E%3CP%3EHow%20about%20creating%20a%20new%20SharePoint%20permission%20group%20-%20call%20it%20'Other%20Site%20Visitors'%20or%20some%20such%20thing%2C%20and%20add%20people%20to%20it%20from%20the%20advanced%20permission%20classic%20view%3F%20Then%20the%20group%20could%20muck%20around%20with%20the%20standard%20Members%2FOwners%2FVisitors%20group%20but%20shouldn't%20even%20know%20that%20your%20custom%20group%20exists.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENot%20a%20good%20solution%20at%20all%2C%20but%20at%20least%20you%20wouldn't%20have%20to%20keep%20recreating%20your%20visitors%20group.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325845%22%20slang%3D%22en-US%22%3ERe%3A%20Bug%3A%20A%20membership%20change%20to%20a%20private%20team%20clears%20the%20associated%20site's%20Site%20Visitors%20access.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325845%22%20slang%3D%22en-US%22%3EYes%2C%20it%E2%80%99s%20in%20sharepoint!%20When%20removing%20a%20member%20from%20teams%20it%20removes%20them%20from%20the%20group%20which%20is%20reflected%20in%20sharepoint%20too!%20Thanks%20for%20investigating%20%3A)%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-325844%22%20slang%3D%22en-US%22%3ERe%3A%20Bug%3A%20A%20membership%20change%20to%20a%20private%20team%20clears%20the%20associated%20site's%20Site%20Visitors%20access.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-325844%22%20slang%3D%22en-US%22%3E%3CP%3ESurprisingly%2C%20%3CSTRONG%3Ethe%20problem%20happens%20independent%20of%20Teams.%3C%2FSTRONG%3E%20I%20created%20a%20team%20site%20in%20SharePoint%20(not%20via%20a%20team%20in%20Teams)%2C%20gave%20%22Everyone%20except%20external%20users%22%20Read%20access%20via%20%22Share%20site%20only%22%2C%20then%20removed%20a%20team%20member%3A%26nbsp%3B%3CBR%20%2F%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20296px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F70991iED1243DCBA99C2C5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22PicPick%202019-01-25%20135821.png%22%20title%3D%22PicPick%202019-01-25%20135821.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3ESome%20time%20later%20I%20checked%20and%20Site%20visitors%20was%20cleared.%20So%20the%20bug%20is%20not%20Teams%20related%20at%20all%2C%20just%20a%20SharePoint%20issue%20(sheesh).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20look%20for%20how%20to%20move%20this%20article%20to%20the%20SharePoint%20community.%20If%20I%20can't%20move%20it%2C%20I%20will%20create%20there%20and%20see%20if%20I%20can%20delete%20from%20here.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-324592%22%20slang%3D%22en-US%22%3ERe%3A%20Bug%3A%20A%20membership%20change%20to%20a%20private%20team%20clears%20the%20associated%20site's%20Site%20Visitors%20access.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-324592%22%20slang%3D%22en-US%22%3EInteresting!%20I%20will%20try%20to%20recreate%20this%20tomorrow%20morning!!%3CBR%20%2F%3E%3CBR%20%2F%3EAdam%3C%2FLINGO-BODY%3E
Roy_F
Occasional Contributor

The site pages of a private team in Teams are intended to be our team's public interface. I use "Invite People" to "Share site only", giving "Everyone but external users" Read access and it works as expected. However, when I later add or remove a team member, within a few minutes (5-60), the Site visitors access is cleared - ouch!

 

I've tried all sorts of paths to avoid the problem, such as editing members from the team in Teams, editing from the site via Add Members, no luck. I tried editing Site visitors via Invite People and by editing the Site Visitors group directly, no luck (problem still occurs). I can't find a way to avoid the bug, so all I can recommend to our users is how to deal with the problem, knowing that it will occur.

 

Workaround, for add/remove team members:

  1. Record the "Site visitors" information for the site.
  2. Add or remove team members.
  3. Wait for Site visitors to be cleared (5m, 30m, 60m?).
  4. Restore "Site visitors".

This workaround is error prone, in that users will likely forget to do it, and painful, since they may not remember what they had for visitor access, so can't restore it properly.


Note: I can't find where to report a "bug". If others will confirm this is a bug and tell me how to go about getting Microsoft's attention, I will appreciate the help. If you try to reproduce, don't forget to uncheck "send mail" when giving everyone read access. :)

5 Replies
Highlighted
Interesting! I will try to recreate this tomorrow morning!!

Adam

Surprisingly, the problem happens independent of Teams. I created a team site in SharePoint (not via a team in Teams), gave "Everyone except external users" Read access via "Share site only", then removed a team member: 
PicPick 2019-01-25 135821.png

Some time later I checked and Site visitors was cleared. So the bug is not Teams related at all, just a SharePoint issue (sheesh).

 

I'll look for how to move this article to the SharePoint community. If I can't move it, I will create there and see if I can delete from here.

Yes, it’s in sharepoint! When removing a member from teams it removes them from the group which is reflected in sharepoint too! Thanks for investigating :)

So it seems that the group takes over control of the standard SharePoint Group.

How about creating a new SharePoint permission group - call it 'Other Site Visitors' or some such thing, and add people to it from the advanced permission classic view? Then the group could muck around with the standard Members/Owners/Visitors group but shouldn't even know that your custom group exists.

 

Not a good solution at all, but at least you wouldn't have to keep recreating your visitors group.

The problem isn't that removing a member also removes them from the associated group, the problem is that adding or removing a "member" removes "Everyone except external users" (EEEU) from Site Visitors. That action doesn't completely clear visitors, it leaves other people with access, but removes EEEU. My suspicion is that if the "member" being added or removed is in a group in Visitors, that group is removed. That is, if Bob is a team member and EEEU is in site Visitors (which covers everyone, including Bob), and I remove Bob as a member, that should not remove EEEU from Site Visitors - clearly a bug. It would only take a few minutes to confirm, but it would be nice if someone from MS would confirm this bug, properly characterize it and provide a workaround, if there is one. 

Related Conversations
Tabs and Dark Mode
cjc2112 in Discussions on
46 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Security Community Webinars
Valon_Kolica in Security, Privacy & Compliance on
13 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies
Extentions Synchronization
Deleted in Discussions on
3 Replies