Connect a provider
Install the GitHub Forge and Lens Apps and check their connection states.
What you'll have
The GitHub Forge and Lens Apps connected for the intended account.
The supported connection flow installs the GitHub Forge and Lens Apps. It doesn’t connect every tool listed in the provider reference. You need permission to manage integrations and permission to install the Apps on the chosen GitHub account.
Open Integrations in the organisation settings.
Result Integrations shows separate Forge and Lens cards, with the current account and connection state where an installation exists.
Select Install Forge. Choose the GitHub account and repositories for this workspace’s work.
Result GitHub opens its installation screen for Forge. You can check the account, requested permissions and repository access before accepting.
Complete GitHub’s installation and return to Integrations. An organisation owner may need to approve a pending request in GitHub.
Result The application checks the installation. The Forge card reports Connected when that installation is ready.
Select Install Lens and complete its GitHub installation for the same account. Check the account and repository selection on both cards.
Result The Lens installation uses the same account. Both cards report their own connection state.
If this doesn't work
If installation fails, read Details for its reason and trace identifier. Ask an administrator to resolve a permission refusal. Use Try again after correcting a failed installation, or Check again when confirmation times out. A pending approval needs the GitHub organisation owner’s action. Don’t disconnect a working App merely to retry confirmation. If the tool you want has no installation control, its setup is unavailable; don’t enter its credentials elsewhere.
Both GitHub Apps are connected for the intended account. This grants only the actions allowed by their actual permissions and repository access. It doesn’t select another provider for Issues, Docs or Dashboards.