Support Center/Connecting GitHub to Your Organization

Connecting GitHub to Your Organization

Learn how to connect your GitHub organization to Helm ADE using a GitHub App installation for secure repo access.

Connecting GitHub to Your Organization

Helm ADE integrates with GitHub through a GitHub App installation, providing secure access to your organization's repositories. This article explains how to connect GitHub at the organization level and manage the connection.

Overview

When you connect GitHub to your Helm organization:

  • Helm installs a GitHub App on your GitHub organization
  • You control exactly which repositories Helm can access
  • All members of your Helm org can use connected repos for projects
  • Repository access is managed through GitHub's native App permissions

Who Can Connect GitHub

Only organization Owners and Admins can:

  • Initiate the GitHub connection
  • Update repository access permissions
  • Disconnect GitHub from the organization

Members and Viewers can view the connection status but cannot modify it.

Connecting GitHub

Step 1: Navigate to Organization Settings

  • Open Helm ADE and ensure you're in the correct organization
  • Click on Organization Settings in the sidebar or header
  • Find the GitHub section
  • Step 2: Start the Connection Flow

  • Click the Connect GitHub button
  • A new browser tab opens to GitHub's App installation page
  • Sign in to GitHub if prompted
  • Step 3: Install the GitHub App

  • Select your GitHub organization from the list
  • Choose which repositories Helm can access:
  • - All repositories - Access all current and future repos - Only select repositories - Choose specific repos to grant access
  • Click Install to complete the installation
  • Step 4: Confirm the Connection

    After installation, you'll be redirected back to Helm. The connection status will show:

    • Connected status badge
    • The GitHub organization name and avatar
    • The date the connection was established

    Managing Repository Access

    Repository access is managed through GitHub's native interface:

  • Go to your GitHub organization settings
  • Navigate to Installed GitHub Apps
  • Find the Helm ADE app and click Configure
  • Update repository access as needed
  • Changes to repository access take effect immediately in Helm.

    Disconnecting GitHub

    To remove the GitHub connection:

  • Navigate to Organization Settings > GitHub
  • Click the Disconnect button
  • Confirm the disconnection when prompted
  • What Happens When You Disconnect

    • Existing project-to-repo bindings become inactive
    • Clone operations will fail for affected projects
    • You can reconnect at any time to restore access
    Note: Disconnecting from Helm does not uninstall the GitHub App. To fully remove the app, also uninstall it from your GitHub organization settings.

    Connection Status

    The connection can be in one of these states:

    StatusDescription
    Not ConnectedNo GitHub App installed for this org
    ConnectedGitHub App is installed and working
    ExpiredThe installation token has expired (re-authenticate)
    RevokedThe App was uninstalled from GitHub

    Troubleshooting

    "Connect GitHub" button doesn't work

    • Ensure you have Owner or Admin role in the Helm organization
    • Check that pop-up blockers aren't preventing the GitHub window from opening
    • Try using a different browser if issues persist

    Connection shows "Expired" status

    The GitHub App installation token needs to be refreshed:

  • Click Reconnect (or disconnect and connect again)
  • Complete the GitHub authorization flow
  • Repositories aren't showing up

    If you just added repositories to the GitHub App:

  • Wait a few moments for the change to propagate
  • Refresh the Helm page
  • Check that repositories are properly configured in the GitHub App settings
  • "Unauthorized" error (403)

    You need Owner or Admin role to manage the GitHub connection. Contact your organization admin if you need elevated permissions.

    Security Considerations

    • Least privilege: Only grant access to repositories your team needs
    • Regular audits: Review connected repositories periodically
    • Revoke if compromised: Disconnect immediately if you suspect unauthorized access
    • Installation tokens: Helm uses short-lived installation tokens, not personal access tokens

    Related Topics