Connecting Your VCS
Use the provider's current setup guide, then check the selected account before managing subscription seats. Signing in, selecting an account and enabling repositories are separate steps.
Supported providers
| Provider | Connection | Setup |
|---|---|---|
| GitHub | OAuth sign-in plus GitHub App installation | GitHub |
| GitLab.com | OAuth sign-in plus a repository PAT | GitLab.com |
| Self-hosted GitLab | Instance SSO or token sign-in; personal/group scope | Self-hosted GitLab |
| Azure DevOps | OAuth sign-in plus a shared organization PAT | Azure DevOps |
| Bitbucket Cloud | OAuth plus selected workspace | Bitbucket |
GitHub
In Repositories, use Add Repositories to select App installation access on GitHub. OAuth sign-in alone does not install the App. Follow the provider guide for organization approval and selected-repository access.
GitLab
Open Repositories → Enable Repositories. On GitLab Repositories, choose Configure token or Update token, paste into Token and choose Save token. The current form lists api and read_user; webhook operations require write-capable API access and the token owner's project rights. A read-only read_api setup does not establish webhook-management access.
For self-hosted GitLab, use its separate instance sign-in and repository screen. A GitLab.com PAT form is not a place to enter a self-hosted server URL.
Azure DevOps
Select the organization and complete the Organization PAT form at /azure/pat. The current form lists Code Read/Write, Build Read/Execute, Work Items Read/Write and Member Entitlement Management Read. Existing shared PAT replacement is restricted to the configuring account or authorized account admins. Then open Repositories → Manage Repositories.
Bitbucket
Select a workspace after OAuth sign-in, then use Repositories → Enable Repositories. The hosted flow does not require an app password. Provider webhook rights and active workspace scope still apply.
Token security
Keep integration credentials private and rotate them through the correct provider-specific control. Account switching does not transfer credentials, repository permissions, seats or billing between accounts. See API Keys and Tokens and Roles and Permissions.
Verify the Connection Before Managing Seats
- Sign in with the provider identity intended to access the repositories.
- Select the owning account: personal/organization for GitHub, personal/group for GitLab, the connected instance for self-hosted GitLab, an organization for Azure, or a workspace for Bitbucket.
- Complete that provider's credential/App installation flow using its detailed guide above.
- Enable the intended repositories or grant their GitHub App installation access, then verify they appear in the active account.
- Check an eligible test review and its completed status.
- Open Subscription in that same account when assigning seats or inspecting paid feature access.
For example, enabling repositories in a company GitHub installation does not assign subscription seats in your personal account. Before changing a subscription, check the current account and the developer identities associated with it.
Common Connection Problems
| Symptom | Check |
|---|---|
| Provider login succeeds but repositories are absent | Complete App/token configuration, check account selection and confirm provider repository access. |
| A repository is listed but cannot be enabled | Inspect the account-scope and provider notification-permission error. Listing and enabling have different requirements. |
| Repository operations work but Analytics is locked | Check the account plan and developer's Analytics seat/access separately. |
| Subscription administration is refused | Check the corresponding account/subscription administration authorization; repository access alone is insufficient. |
| Seat/member lookup fails in Azure | Check the selected organization and shared PAT, including the displayed Member Entitlement Management scope. |
| Connection breaks after a token expires | Replace it through the provider-specific control, then verify repository access and a test review. |
Use the provider guide for setup details and Managing Seats for assignment and removal behavior. Connecting a VCS, enabling a repository and assigning a seat are separate steps with separate verification.

