Based on the research, this behavior is likely related to how GitHub SSO and email verification are configured in your organization. Here's what's happening: 1. When you log in with your generic company email, it's properly configured in your organization's SSO settings and thus appears in the member list. 2. The ability to log in with your individual company email, despite it not showing in the organization's members, suggests one of these scenarios: a. The email is associated with your GitHub account but wasn't included in the SSO configuration for your organization b. There might be a mismatch between the emails configured in GitHub and the ones recognized by your organization's SSO settings To resolve this, you should: 1. Check all email addresses associated with your GitHub account (GitHub Settings > Emails) 2. Verify which emails are verified and primary in your GitHub settings 3. Contact your organization's admin to ensure: - The correct email addresses are included in the SSO configuration - The directory sync settings (if used) are properly configured to recognize all valid company email addresses The fact that removing GitHub authorization didn't resolve the issue suggests this is more related to the underlying SSO configuration rather than just the GitHub authorization itself. For security best practices, you should: 1. Use only one email for organizational access 2. Have your organization's admin review the SSO configuration 3. Consider implementing SCIM provisioning (if on an enterprise plan) to better manage user access and visibility If this continues to be an issue, your organization's admin should review the SSO configuration details in the Prefect Cloud documentation (https://docs-3.prefect.io/v3/how-to-guides/cloud/manage-users/configure-sso) to ensure all settings are properly configured.