Edit Source Account

Validate provider access before saving. Secrets are encrypted and never displayed back.

Help Connected Sources
Update Provider Access

Edit Connected Account

Select GitHub or Bitbucket and enter only the credentials required for that provider. Saved secrets are protected. Leave secret fields blank to keep the current value.
GitHub Setup
Use a GitHub App for organization-wide access or a personal access token for quick setup. See GitHub help
Leave blank to keep saved PEM key.
Token Guide
Open GitHub Apps
Bitbucket Setup
Use a scoped Bitbucket API token with workspace and repository read access. Enter the Atlassian account email used to create the token, not the Bitbucket username. The workspace slug must match the Bitbucket URL, for example solutionbowl. See Bitbucket help
Credentials are validated before the account is updated. Secret fields can be left blank to keep the existing value. For GitHub App, App ID and Installation ID must be numeric values from GitHub. For Bitbucket, enter the exact workspace slug from the Bitbucket URL. Secrets are stored encrypted.
Cancel