Quangence
Build

Contents

Documentation · GitHub

GitHub

Connecting GitHub is optional. When you connect, you install the Quangence GitHub App for your user account or organization. The backend only uses permissions you grant on GitHub’s install screen (for example, which repositories the app may access).

Why connect GitHub?

Use GitHub when you want workflows that depend on repository context—such as reading code, opening or reviewing changes, or staying aligned with how your team already works in GitHub. If you only need conversational help without repo access, you can skip this entirely.

What you are granting

During install, GitHub asks you to pick where the app is installed (account or org) and which repositories it can access (all, selected, or as allowed by your org’s policies). Quangence respects that scope. GitHub uses one installation id per account—you can add more repositories to that same installation later. You can disconnect anytime from the app or from GitHub’s app settings.

Screenshot placeholder — GitHub “install app” or repository access step. Capture the real flow for your deployment.

Connect GitHub

  1. Open Settings in the Quangence app.
  2. In the connectors area, choose Connect GitHub App (or the equivalent control shown in your build).
  3. Complete GitHub’s installation wizard: pick the account or organization and repository access.
  4. Return to Quangence. Your connections should list the new install. Use Refresh if the list has not updated yet.

Screenshot placeholder — Settings → GitHub / connectors list with at least one connected installation.

Manage access

For each listed connection:

  • Add more repositories — Opens GitHub’s settings for that installation so you can grant access to additional repos using the same installation id (no need to install the app again).
  • Disconnect — Removes that installation from Quangence’s perspective; revoke or adjust the app on GitHub if you need to fully uninstall.

If your organization uses OAuth App restrictions or SAML, follow your org’s process; the install must be allowed by your GitHub org admins.

Security and data

  • Treat repository access like any production integration: use least privilege (only the repos you need).
  • For privacy and data handling, see and .