How do large organizations deal with 1,500 team cap?

[tuisk909]

Body

Hi,

I work with a large organization that has recently started using GitHub enterprise and we looking for suggestions of how other organizations deal with the 1,500 team limit.

We were planning on setting it up so that each new repo created will automatically be assigned a new write and admin team but are worried that over time this will see us exceed the 1,500 team limit.

Another option would be to have a single write/admin team for multiple repos based on company departments or teams. However issue with this is that it means that some users could have access to repos that we they really don't need access to.

So basically we are trying to find out what's the best way for assigning access essentially without requiring multiple orgs?

Thanks

[queenofcorgis]

Hey @tuisk909 - thanks for posting this is a great question - I'm going to make sure it is highlighted in June's Enterprise roundup so you're more likely to get a few perspectives here ❤️

[vegardx]

Hi,

I'm very keen on this discussing this to get other peoples perspectives on this. Feel free to reach out to me directly using the e-mail in my profile.

We've discussed doing all the role mapping in Entra ID, where every repository role mapped to a unique team, which was mapped to a unique Entra ID group. But this doesn't really scale with the limit of 1500 teams per organization. It's also unknown how well this would work with IdP team synchronization.