Multiple GitHub organizations

If you have multiple GitHub organizations where your developers are active, you might want to view data from all of them. This article explains the various options available in Swarmia for connecting your company's multiple GitHub organizations.

Option 1: Syncing data from multiple GitHub organizations to a single Swarmia organization

It is possible to sync data from multiple GitHub organizations to a single Swarmia organization, so that you can see all the data at once.

This option supports both GitHub Cloud and a GitHub Enterprise Server.

This approach is a good choice when:

• There are no internal access control concerns. Everyone from your company will see all data from all of your connected GitHub organizations.

• People are working across GitHub organizations. With this approach, you can easily see a person’s work across all the organizations.

To use this approach follow the steps for connecting GitHub code hosting platform.

If you have already created multiple Swarmia organizations for each GitHub organization, see Combining existing Swarmia organizations.

If you are using GitHub to authenticate users, connecting multiple GitHub organizations impacts who can log in to your Swarmia organization. Read more on Access control with multiple GitHub organizations.

Option 2: Multiple Swarmia organizations

Alternatively, It is possible to sign up each of the GitHub organizations as completely separate Swarmia organizations and invite specific people to each of them.

If a user with access to multiple organizations logs in to Swarmia, they can choose to which of the organizations they want to log in. To switch organizations, the user needs to log out and back in.

This approach is a good choice when:

• There is a need to limit access control (all users don’t belong to all GitHub organizations and shouldn’t see data from orgs that they don’t belong to).

• People mostly don’t work across multiple GitHub organizations. If they do, this approach is not ideal, as it will be difficult to get a full picture of a person's work due to being only able view it by one organization at a time.

To use this approach, install the Swarmia GitHub app on each of your GitHub organizations. Then, when you log in to Swarmia, you can choose which organization to log into. To invite team members to the organizations, send them the invite link that you can find on the Contributors page under Settings.

Combining existing Swarmia organizations

If you have two or more existing Swarmia organizations and want to merge them into one, a manual step-in by our engineering team is required.

Please reach out to us at [email protected], tell us which one of the multiple connected GitHub organizations you want to be the primary one, and then we'll be happy to set things up for you. The primary organization selection affects which Swarmia organization settings will be used for the merged organization. Also familiarize yourself with Multiple GitHub organizations and let us know which access control option would suit you.

Please note that settings and configurations, such as working agreements or ignored pull requests, won't be carried over from the non-primary organizations.

Merging multiple GitHub organizations to a single Swarmia organization is only available in our paid plans.