Connecting Git services

Required role

Only Super Admins can view, add, update, or disconnect Git service connections. Other roles cannot see Integrations or access it directly by URL.

Before you start

A personal access token (PAT) or equivalent access token for the Git service
An Integration Token Name that identifies the token
A server address reachable from XEIZE if you use a server other than GitHub.com or GitLab.com

The connection screen shows the same api permission guidance for every Git service. This is not a provider-specific scope name or a statement of minimum permissions. Grant the token the permissions needed to:

Validate the token
List accessible organizations, groups, or projects
List target repositories and read their source code

Choose the token type and minimum permissions according to your organization's Git service policy and XEIZE installation. Do not record token values in documentation, chat, or logs.

Service URLs

Service	Default destination	Custom URL	Supported environment
GitHub	`https://github.com`	Optional	GitHub.com or a separately hosted GitHub server
GitLab	`https://gitlab.com`	Optional	GitLab.com or a separately hosted GitLab server
Bitbucket	Not filled automatically	Required	Self-hosted Bitbucket Data Center or Server

Bitbucket connections support only self-hosted Data Center or Server installations. You must enter the server URL.

Connecting GitHub

Menu: Integrations > GitHub > Connect

Select Integrations in the sidebar.
Select Connect on the GitHub card.
Enter the GitHub access token in Account Credential.
Enter a descriptive Integration Token Name, such as github-production.
For a server other than GitHub.com, enable Use Custom GitHub URL and enter its URL, such as https://github.company.com.
Select Connect.
Confirm the success message and the connection name and URL under Current Connection.

Without a custom URL, the connection uses https://github.com.

Connecting GitLab

Menu: Integrations > GitLab > Connect

Select Integrations in the sidebar.
Select Connect on the GitLab card.
Enter the GitLab access token in Account Credential.
Enter an Integration Token Name, such as gitlab-platform.
For a server other than GitLab.com, enable Use Custom GitLab URL and enter its URL, such as https://gitlab.company.com.
Select Connect.
Confirm the success message and connection details.

Without a custom URL, the connection uses https://gitlab.com.

Connecting Bitbucket

Menu: Integrations > Bitbucket > Connect

Select Integrations in the sidebar.
Select Connect on the Bitbucket card.
Enter the Bitbucket access token in Account Credential.
Enter an Integration Token Name, such as bitbucket-dc-production.
In the required Bitbucket Server URL field, enter the Data Center or Server URL, such as https://bitbucket.company.com.
Select Connect.
Confirm the success message and connection details.

Unlike the custom URLs for GitHub and GitLab, the Bitbucket server URL cannot be omitted.

Managing multiple tokens

You can register multiple connections for each Git service. The connection screen supports:

Connection selection: choose the connection to manage from the list.
Add: create another connection for the same Git service.
Update: change the connection name, token, or URL. You must enter a valid token again when updating.
Disconnect: deactivate the selected connection.

The browser remembers the last connection selected for each Git service and preselects it on the Add Project screen.

Once disconnected, a connection cannot be selected for new projects. Before disconnecting it, check whether any projects use it.

Troubleshooting connections

Connection fails

Check that the token has not expired or been revoked.
Check that it can access the target organization and repositories.
Enter the complete custom server URL, starting with https://.
For self-hosted servers, check that XEIZE can reach the server.

Organizations or projects are missing

Enter the token again through Update, then check the connection.
Check that the token owner can access the target organization, group, or Bitbucket project.
If service or organization policy requires single sign-on (SSO) authorization or approval for personal access tokens, contact the service administrator.

A different token is being used

Reselect the intended connection in the Integration list on the Connect or Add Project screen.