LogoLogo
Book a demoLog in
  • Swarmia documentation
  • Getting started
    • Get started in 15 minutes
    • Integrations
      • GitHub
        • GitHub Enterprise Server
        • Multiple GitHub organizations
        • Forked repositories
        • Troubleshooting
          • Reinstalling the Swarmia GitHub app
          • Updating app permissions
          • Installing Swarmia outside of GitHub Marketplace
      • Jira
        • Jira Server and Jira Data Center
        • Multiple Jira organizations
      • Linear
        • Private Linear teams
        • Disconnect Linear
      • Slack
        • Private Slack channels
      • Authentication
        • Google Single Sign-On
          • Frequently asked questions
        • Okta Single Sign-On
      • HR systems
      • Data export
        • Data cloud
        • Export data as a CSV file
      • Other integrations
        • Other issue tracker integrations
        • Other source code hosting integrations
  • Configuration and data quality
    • Teams & members
      • Creating & managing teams
        • Teams API
      • Contributors
      • Roles and permissions
      • Inviting team members
    • Issue tracker configuration
      • Jira configuration
      • Jira best practices
      • Linear configuration
    • Pull request exclusions
    • Linking pull requests to issues
    • Investment categories
    • Deployments
      • Generate deployments from merged pull requests
      • Generate deployments from GitHub deployments
      • Generate deployments from GitHub checks
      • Generate deployments via the API
        • Generate deployments for monorepos via the API
    • Sprint configuration
  • Use cases
    • Improve pull request flow
      • Pull request insights
      • Reducing pull request cycle time
      • Review code faster
      • Managing pull requests in progress with the Pull Request view
      • Diagnosing low pull request throughput
      • Analyzing pull request batch size
  • Improve your team's focus
    • Optimizing issue cycle time
    • Analyzing activity patterns on Work Log
    • Grouping activity on the Work Log view
    • Focus summary
  • Balance engineering investments
    • Activity and effort-based models
    • Categorizing work
    • Common problems with balancing engineering investment
  • Deliver strategic initiatives
    • Forecasting initiatives
  • Capitalize software development costs
  • Run developer experience surveys
    • Creating a survey
    • Managing surveys
    • Viewing and sharing survey results
    • How we show your survey responses
    • Survey communication guide and templates
  • Track DORA metrics
    • Automatic change failure detection
    • How Swarmia links PRs to deployments
  • Coach software developers
  • Get visibility into your CI pipeline
  • Continuous improvement
    • Working agreements
  • Notifications
    • Team notifications
    • Personal notifications
  • Retrospectives with Swarmia
  • Metrics & definitions
    • Pull request cycle time
      • What's the difference between "Change lead time" and "Pull request cycle time" metrics in Swarmia?
    • Issue cycle time
      • Defining issue lifecycle and cycle time
    • Developer effort (FTEs)
  • DORA metrics
    • Change lead time
    • Deployment frequency
    • Mean time to recovery
    • Change failure rate
  • Throughput
  • Time to deploy
  • Batch size
  • Flow efficiency
  • Scope creep
  • Sprints
  • Frequently asked questions
    • How do you treat weekends in metrics?
    • Tracking squashed commits
    • How do merge queues affect my metrics?
    • Why is my commit not visible in Swarmia?
    • How do I account for people leaving my organization?
  • Resources
    • Security & data retention
      • Data security
      • Data access
      • Swarmia IP Addresses
      • Single Sign-On (SSO) / SAML
      • Can I get a copy of the SOC 2 Type II audit report?
      • Deleting your organization
  • Pricing & plans
    • Compare plans
    • Free plan
    • Do I need a credit card to start a free trial?
    • What are the differences between the individual modules and the standard plan?
    • How do you determine the number of developers for billing?
    • What happens to customers with the Lite plan after the December 2024 pricing and plan change?
  • Changelog
On this page
  • Option 1: Multiple Swarmia organizations
  • Option 2: Syncing data from multiple GitHub organizations to a single Swarmia organization
  • Access control with multiple GitHub organizations

Was this helpful?

  1. Getting started
  2. Integrations
  3. GitHub

Multiple GitHub organizations

PreviousGitHub Enterprise ServerNextForked repositories

Last updated 1 month ago

Was this helpful?

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: Multiple Swarmia organizations

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, simply install the Swarmia 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 under Settings.

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

Alternatively, 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 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, as the first step, install the Swarmia app on each of your GitHub organizations. The next step of merging these multiple Swarmia organizations into one requires a manual step by our engineering team. Please reach out to us at , 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. Please note that merging multiple GitHub organizations to a single Swarmia organization is only available in our paid plans.

Currently, it is not possible to combine data from GitHub Cloud and a GitHub Enterprise Server organizations. In this case, you should instead use Option 1.

Access control with multiple GitHub organizations

When syncing data from multiple GitHub organizations to a single Swarmia organization, everyone who can access Swarmia will be able to see data from all connected GitHub organizations.

In this scenario, you can choose between several options for access control:

  1. User must have access to all connected GitHub organizations on GitHub to be allowed logging into the Swarmia organization. This ensures Swarmia users will never have more access than they would already have on GitHub. This is the default.

  2. User must have access to at least one connected GitHub organization on GitHub to be allowed logging into the Swarmia organization. This is more convenient, as you don't need to add all users to all organizations GitHub-side. You may opt into this access control setup during organization merge, or later, by reaching out to our support.

  3. User must have access to your external SSO provider (such as Okta or Google SSO). In this case, users logging into your Swarmia organization will see all data from all connected GitHub organizations, regardless of the access control configuration GitHub-side. This is the default when using an external SSO provider.

Contributors page
hello@swarmia.com