# GitHub App: Connecting your Bitrise workspace to multiple GitHub organizations

**URL:** <https://discuss.bitrise.io/t/github-app-connecting-your-bitrise-workspace-to-multiple-github-organizations/25348>\
**Category:** Changelog\
**Tags:** feature-update\
**Created:** [June 26, 2025, 2:55pm UTC](https://discuss.bitrise.io/t/github-app-connecting-your-bitrise-workspace-to-multiple-github-organizations/25348 "2025-06-26T14:55:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeremyp](https://sea2.discourse-cdn.com/flex016/user_avatar/discuss.bitrise.io/jeremyp/32/5490_2.png) [@jeremyp](https://discuss.bitrise.io/u/jeremyp)\
**Post date:** [June 26, 2025, 2:55pm UTC](https://discuss.bitrise.io/t/github-app-connecting-your-bitrise-workspace-to-multiple-github-organizations/25348/1 "2025-06-26T14:55:48Z")

</div>

Does your company have code located in more than one GitHub organization/account? If so, you may have come across this limitation: the Bitrise GitHub App only allows you to connect one of your GitHub orgs at a time. This can lead customers to implement messy workarounds.

Not any more! Our GitHub App now allows you to connect a single Bitrise workspace to multiple GitHub organizations.

### What’s new?

Admin users who have installed the Bitrise GitHub App will see a new **Add GitHub account** button in the Workspace Settings \> Integrations \> GitHub page. You can use this to connect up to 10 GitHub accounts/organizations to your workspace.

 ![Screen Shot 2025-06-26 at 3.31.30 PM](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/9/9c974d2beacea58a31836432f76c5b651aadb7b2.png)

Find out more about enabling the Bitrise GitHub App in our [Devcenter](https://devcenter.bitrise.io/en/connectivity/github-app-integration.html#installing-the-github-app-integration).

### Why this is useful?

We’ve come across many customers who need their Bitrise builds to access multiple GitHub organizations. There are a variety of reasons for this, here are two of the most common:

- Large customers often have modularised code stored in different GitHub organisations
- The team is migrating code to a new GitHub organisation e.g. when moving to a monorepo. It’s important to test that the CI works with code in the new organization while maintaining the CI connection to the current one as a failsafe

With this update you can simply change a setting rather than resorting to messy workarounds, like reverting to a less secure integration via OAuth, to keep build running.

Happy building!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/bitrise/original/2X/d/d901cf2aad020f2dd11918afc89ec2089bb87b35.png) [@system](https://discuss.bitrise.io/u/system)\
**Post date:** [September 24, 2025, 2:56pm UTC](https://discuss.bitrise.io/t/github-app-connecting-your-bitrise-workspace-to-multiple-github-organizations/25348/2 "2025-09-24T14:56:36Z")

</div>

This topic was automatically closed after 90 days. New replies are no longer allowed.