Accounts & authentication

Register Git host accounts so you can choose which identity and authentication to use for each repository. The choice is written to Git’s native configuration (.git/config, the credential store, SSH). It applies the same way in the terminal too.

The Accounts settings screen, listing token, OAuth, and SSH account cards, each with a server-type badge and an authentication-method badge

Where accounts are managed

Settings → ParalleLane → Accounts

Add, edit, and delete every account registered on the machine.

Settings → Projects → Accounts

Choose the account to use for each repository. The moment you choose it, it’s written to that repository’s Git configuration.

Adding an account

PRO only. Basic can register up to 2 accounts in total, and self-hosted (GitHub Enterprise, GitLab Server, and Bitbucket Server) accounts are Pro only. When you hit the limit, the Add account button gets a PRO badge.

Click Add account in the Settings → ParalleLane → Accounts panel header and choose a platform (GitHub / GitHub Enterprise / GitLab / GitLab Server / Bitbucket / Bitbucket Server / SSH) to open the matching form. Fill in Label (optional), git user.name, and git user.email, which are common to all, then click Add.

The Add GitHub account modal, with the authentication type selector and the git user.name and user.email input fields

GitHub and Bitbucket Cloud show an Authentication Type dropdown.

In GitHub, new accounts start with Sign in with GitHub (OAuth) preselected. To use a token, switch to Personal Access Token.
In Bitbucket Cloud, only App Password is available.

Personal Access Token
GitHub OAuth
SSH key

host is fixed for Cloud, and entered manually for Enterprise/Server.
username appears only for Bitbucket, and is required.
token takes the issued token you paste in (GitHub ghp_…, GitLab glpat-…, a Bitbucket app password, and so on). An Open token creation page link and a Required scopes (minimum) note are provided alongside it.
Validate fills in the empty name and email fields on success, and saves the username and avatar.

The token is stored in the OS keychain and never lands on disk in plain text.

If you entered a new token, Validate must succeed before Add / Save becomes enabled. When editing an existing account, leaving the token field blank keeps the stored token as is.

Connects an account via browser sign-in (device code).

Start sign-in

Click Sign in with GitHub.

Confirm the code and authorize in the browser

A user code appears (for example, PLNE-2026). Copy it with Copy code, then open the browser with Authorize on GitHub to enter and approve it.

Add the account after approval

Once approval finishes, the card changes to Signed in as @username and the name and email fill in. Click Add to save it.

The Add GitHub account modal showing the device code PLNE-2026, the Authorize on GitHub button, and a message that the card is waiting for approval

OAuth sign-in works only for github.com accounts. GitHub Enterprise, GitLab, and Bitbucket Server use token authentication only.

If the running build has no GitHub sign-in configured, adding a new account falls back to token entry for the authentication type. Accounts already saved with OAuth keep their existing credentials and continue to work.

An SSH account is not tied to a specific host. It only specifies a key.

In Select key…, choose an existing key from ~/.ssh or generate one with + Create new SSH key.
Copy it with Copy public key, then register it in the Git host’s SSH key settings. A link such as Register on GitHub opens the registration page directly.
Open SSH folder opens ~/.ssh in Finder.

For an SSH account to actually be used, the repository’s remote URL must be in SSH format (git@…). An HTTPS remote shows a warning.

Checking connection status

Each account card shows the label, name and email, and badges for the server type and authentication method. The global default account gets a Global badge, and an account applied to a specific repository gets a # repository-name badge.

For Token/OAuth accounts, Online / Offline and the username appear next to the title, and Check status revalidates the token and refreshes the display and avatar.
For SSH accounts, clicking Check status opens a popover for choosing which hosts to test, and hosts that authenticate successfully are listed on the card.

Use the card’s Edit to change the label, name, email, and token, and Delete to remove the account together with its token from the keychain.

Delete is disabled for the global default account or for any account applied to a repository. First switch to a different account, for that repository and in Default account under Settings → ParalleLane → Git.

Assigning an account to a repository

In Settings → Projects → Accounts, pick a repository, then choose Global (machine-wide setting) or a registered account from the Account for this repository dropdown. The choice applies to the repository’s Git configuration immediately.

The Accounts settings screen for choosing the account of the repository selected in the Projects tab

Choice	What gets written
Global	Removes the repository’s local override and follows the machine-wide Git configuration.
SSH account	Writes `user.name`/`user.email` and `core.sshCommand` to the repository’s local configuration.
Token account	Writes `user.name`/`user.email`, updates the user info in the remote URL, and saves the token to the Git credential store.

The account applies to exactly one remote, origin. Set the global default account in Default account under Settings → ParalleLane → Git.

Avatars

Token/OAuth accounts fetch the profile picture from the host API, and fall back to email-based Gravatar on failure. SSH and Global accounts use Gravatar. You can refetch it from the Avatar row on a saved account’s Edit screen. Every account shows a Sync from Gravatar button, and GitHub accounts also show Sync from GitHub. If you changed the email or authentication method, click Save first to enable the sync button.

Fixing authentication errors

When Push, Pull, Fetch, or Clone fails, the app shows the underlying Git error along with a likely cause.

Message	What to check
Path-specific credential mismatch	Turn off the repository’s `credential.useHttpPath`, or register a credential that matches that path.
No stored HTTPS credential	Reselect the project account and check that the token is still in the OS credential store.
Token or password rejected	Check whether the token expired or was revoked, and verify the username and required scopes.
Insufficient repository permissions	Check the account’s collaborator/team permissions and organization SSO approval.
Repository not found	Check the remote URL and read access to the private repository.
SSH public key rejected	Check that you’re using the correct private key and that the public key is registered with the host.
SSH host key verification failed	Check the `known_hosts` entry and verify that the server key change is legitimate.

The app never reads token values or logs them for error diagnosis. Don’t paste credentials into documents or issues.

Getting started

Basics

Worktrees

Branches & history

Remotes & syncing

Conflicts & comparing

Accounts & settings

Shortcuts

Accounts & authentication

Where accounts are managed

Settings → ParalleLane → Accounts

Settings → Projects → Accounts

Adding an account

Checking connection status

Assigning an account to a repository

Avatars

Fixing authentication errors

​Where accounts are managed

Settings → ParalleLane → Accounts

Settings → Projects → Accounts

​Adding an account

​Checking connection status

​Assigning an account to a repository

​Avatars

​Fixing authentication errors

Where accounts are managed

Adding an account

Checking connection status

Assigning an account to a repository

Avatars

Fixing authentication errors