Setting to enable EMU Enterprises to allow members to collaborate externally

[JinsengIT]

🏷️ Discussion Type

Product Feedback

Body

We are a consulting organization that works with external customers. As such, we need the ability to work in their Organizations and Repos. Also, we need the ability to manage our user accounts through SCIM and Single-Sign-On, so we opted for an EMU enterprise.

Please enable and option to allow Enterprise Managed Users to interact with external organizations and Repos like they can in Azure DevOps.

Our workarounds are to have our staff create personal accounts that are then invited into the customer's environment, or to ask the customer to provide them with an account. A major issue with both of these options is that we do not have the ability to disable their access across all of our systems and our customer's systems like we would if our EMU accounts could be used everywhere.

Thank you.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[Dani-8]

@JinsengIT This is a major, well-known architectural friction point for consulting firms and managed service providers using Enterprise Managed Users (EMU).

Because GitHub EMU accounts are strictly isolated to the owning enterprise namespace (user_shortcode) to prevent cross-tenant data leakage, they cannot collaborate natively outside that enterprise boundaries—unlike Azure DevOps B2B guest access or standard GitHub user accounts.

To help manage security, offboarding, and compliance across external clients today, many consulting organizations rely on these two patterns:

1. Guest EMU Accounts Provisioned inside Client Enterprises (Recommended for Client Compliance)
   • If the client also uses an EMU enterprise, the cleanest approach is having the client provision an EMU account for your consultant via their own Identity Provider (e.g., Entra ID / Okta).
   • When your employee leaves your firm, disabling them in your primary IdP automatically revokes their access across federated SSO applications, and notifying the client allows their IdP lifecycle to instantly suspend the guest EMU account.

2. Enterprise Guest / Multi-Account Provisioning Tools
   • If clients use standard GitHub Organizations (non-EMU), consultants use a dedicated company-managed standard GitHub account tied to their enterprise domain (e.g., username-company).
   • Access control is managed using IdP-driven SCIM/SSO Offboarding webhooks or automated scripts (via the GitHub REST/GraphQL API) to audit and remove external organization memberships during offboarding.

Your point regarding native B2B guest federation for EMU accounts (similar to Azure DevOps Guest Users) is a critical request for consulting workflows!

[queenofcorgis]

Hi @Dani-8 , thanks for participating in GitHub Discussions!

Please note: we’ve clarified our stance on using generative AI tools like ChatGPT within our Community via this announcement. Please review the guidelines to ensure your post meets them as failure to adhere to those rules can result in action taken by our moderator team. 

You can read our updated Code of Conduct and the announcement for more details.

Please feel encouraged to continue engaging in Discussions as your authentic self though. We appreciate you being a part of the Community 🌟