Collaborator limit should not be imposed against forks of paid repositories
Our organization pays for your [excellent] service.
The way we want to collaborate is by having our employees fork the organization's private repository and then submit pull requests back. This allows us to use the pull request as a gateway for code review, and we really like it. It also allows us to better control our "truth" repository (limited access to master/dev branches, no dangling rotting feature branches, etc). (this is no different from the standard open-source method for collaboration)
The problem is that our employees' private forks have a collaborator limit capped at 5. If we're paying for the service, our employees shouldn't have to pay to collaborate with their teammates, even though it happens to be in their account.
We thought we might work around this by creating repositories named <REPO>-<username> for each teammate, but then we couldn't figure out how to submit pull requests because they weren't true forks.
If possible, we wanted to avoid employees working out of the truth repo day-to-day. And they shouldn't have to pay money -- because we did.
What do we do?