Inter-organization Trusts

[mrgenixus]

Select Topic Area

Product Feedback

Body

NOTE: I couldn't find a category that felt like a good place for this feedback; please let me know if there was a better place to put this.

I run a consulting company and it is an ongoing pain to manage my staff's access to client's repos, requiring each client to create a team for my staff and ensuring that departing or separated staff are always removed from all client teams at that time. While we manage potential liabilities from that access through employment contracts, etc, the fact is, contracts cannot in and of themself prevent irreparable harm so mistakes have the potential to be costly, particularly since, at times, our staff has elevated access on client repos.

My request is this: Could I share a team from my organization with the client in a way that allows them to give collaborator access to my team and so that when I remove a member from my organization and they would be automatically removed from organizations teams, that they would be removed from this shared team also.

It would be reasonable, even a specific advantage to me if I paid for additional seats in order for my team to access other organizations repos rather than have the client pay, since this is often a point of contention (e.g. "Why do we need to add so many seats so that one member of your team can work on our project ...").

Though I could not find an exiting suggestion regarding shared teams or inter-organization trusts, I'm sure I'm not the only person who has an ongoing need for this behavior; It's certainly more important than the constant barrage of new AI features I won't use.

[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. ⭐

[shinybrightstar]

Welcome to the GitHub Community, @mrgenixus, we're happy you're here!

You are more likely to get a useful response if you are posting your question(s) in the applicable category, this might help someone give you a nudge in the right direction.

Since the request for inter-organization trust relationships and shared team management is an enterprise-level administrative feature, I've gone ahead and moved it to the Enterprise category for you. Good luck!