GitHub

OAuthDeveloperOrg connection

Org-level connection

GitHub is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.

How to connect

Prerequisites: You'll need a GitHub account with access to the GitHub resources you want to connect.

Click "Connect with OAuth" below to authorize On Belay to access your GitHub account or organization. You'll be redirected to GitHub to approve the connection and select which repositories to grant access to — no credentials to copy or paste.

Ready to connect?

Permissions (scopes)

These are the data scopes On Belay can be granted for GitHub. Your org admin controls which scopes are enabled per group.

Scope	Description	Access
`repo`	Full repository access (code, issues, pull requests)	Read / Write
`read:org`	Read organization membership and teams	Read only
`read:user`	Read user profile data	Read only

Troubleshooting

"redirect_uri_mismatch" error during OAuth

Your OAuth app's authorized redirect URIs don't include the On Belay callback URL. Add https://app.onbelay.ai/api/oauth-callback/github to the allowed redirect URIs in your OAuth app settings.

"invalid_scope" error

The API or scope isn't enabled in your cloud project. For Google integrations, make sure the relevant API (e.g. Google Ads API, Search Console API) is enabled in Google Cloud Console for your project.

Connected but Claude can't access data

Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.

Still stuck? We're happy to help.

Contact support →