Skip to main content
To list a group’s members, its pending invitations and the people with access only to its subgroups or projects, create the token as an Owner of that top-level group. Other roles see direct members only.

​
Create an access token

Use a personal access token, or a group access token for a bot user.

1

Open Access tokens

Sign in to GitLab.

  • Personal access token: Edit profile > Access tokens > Add new token
  • Group access token: open the group, then Settings > Access tokens > Add new token
2

Choose scopes

Select read_api for read-only access, or api to also use write actions. On GitLab Self-Managed with Admin Mode turned on, an administrator also selects admin_mode to read the instance user roster and two-factor status. Set an expiry date that fits your rotation policy.

3

Copy the token

Click Create token and copy it. GitLab shows it only once.

​
Find your instance URL

Leave the instance URL empty for GitLab.com. For GitLab Self-Managed or Dedicated, use the address you open GitLab at, such as https://gitlab.example.com, without a trailing slash or /api/v4. If the instance is behind a firewall, allow inbound HTTPS from StackOne’s IP addresses.

​
Linking the Account from the Hub

1

Navigate to the Hub

Use one of the three Linking Account Methods to access the Hub.
2

Fill out the fields

Fill out the following fields using details from your provider:
  • GitLab Instance URL (Optional)
  • Access Token
3

Connect

  • Click Connect
  • If applicable, the provider will redirect you to a sign-in or authorization page. Complete the provider’s authorization flow.
  • Once authorization is successful, you will see a confirmation popup

If the account linking is successful, you will see the newly linked account in your Accounts page.

​
Next Steps

Webhooks setup

Configure receiving Events for GitLab into StackOne.