<div dir="ltr">Does anyone have experience with controlling access to individual Organizations in GitHub Cloud?  We would like to control access by using Grouper group memberships.  We are successfully using their SAML SSO support.  But... <div><div><br><div>It seems the only attribute GitHub cares about is NameID.  We are currently passing our persistent ID in NameID.  If it's there, they get in. To block access for a user, we would have to NOT send NameID in the assertion, if that's even possible.<input name="virtru-metadata" type="hidden" value="{"email-policy":{"state":"closed","expirationUnit":"days","disableCopyPaste":false,"disablePrint":false,"disableForwarding":false,"enableNoauth":false,"persistentProtection":false,"expandedWatermarking":false,"expires":false,"isManaged":false},"attachments":{},"compose-id":"9","compose-window":{"secure":false}}"></div><div><br></div><div>Is it possible to conditionally NOT send NameID depending on a user's other attributes?  Is there another way to manage GitHub Org access (besides manually)?</div><div><br></div></div><div>Thanks.</div><div>Joanne</div><div><br></div><div>---</div><div><br></div><div><span style="color:rgb(32,33,36);font-family:arial,helvetica,sans-serif">Joanne Schwendner</span><br style="color:rgb(32,33,36);font-family:arial,helvetica,sans-serif"><span style="color:rgb(32,33,36);font-family:arial,helvetica,sans-serif">Senior Developer - </span><font color="#888888">Web, Integration, & Identity Services</font><br style="color:rgb(32,33,36);font-family:arial,helvetica,sans-serif"><span style="color:rgb(32,33,36);font-family:arial,helvetica,sans-serif">Brown University</span> </div><div> <br></div></div></div>