To create projects, Paylood needs access to your Git repositories. The connection happens via OAuth, never touching your passwords.
Supported providers
| Provider | Connection type | Access |
|---|---|---|
| GitHub | OAuth App | Public and private repositories |
| GitLab | OAuth 2.0 | Public and private repositories |
| Bitbucket | OAuth 2.0 | Public and private repositories |
Connect an account
- Open Settings → Git Accounts.
- Click Connect next to the desired provider.
- A window opens at the provider: authorize the requested access.
- You are redirected back to Paylood automatically, and the account shows as connected.
Capture à venir
en/git-providers-connect
Cette capture illustrera la vue correspondante. Elle est générée automatiquement par le pipeline Playwright.
Tip
If you signed up with GitHub, your GitHub account is already linked automatically.
Requested permissions
- GitHub: profile read, email and repository access (
repo). Paylood uses these to list your repositories and install the auto-deploy webhook. - GitLab: profile, user read and repository read.
- Bitbucket: profile, email and repositories.
Permissions are revocable at any time from the provider settings or by disconnecting the account in Paylood.
Managing multiple accounts
You can connect several accounts from the same provider (for example two GitHub accounts). When creating a project, select the account that holds the repository you want.
Disconnecting an account
- Open Settings → Git Accounts.
- Click the disconnect icon of the relevant provider.
- Confirm: the token is removed from Paylood.
Warning
Already-deployed projects keep working after disconnecting a Git account. Only new automatic deployments (webhooks) are suspended.
Troubleshooting
- “Provider not active”: the OAuth token is invalid or was revoked at the provider. Reconnect the account.
- The OAuth window closes without action: disable the pop-up blocker and retry.
- “Connection failed”: check that the provider’s OAuth app is correctly configured (IDs, secrets, redirect URI). Contact your installation administrator.
The OAuth token is encrypted with your Paylood installation’s encryption key before storage. It is never sent back to the browser in plain text.