Skip to main content

Create a GitLab Project Access Token

To connect a repository to Buzzbin, create a Project Access Token in that same GitLab project. This is the safest and simplest starting point because the token is scoped to one repository.

Before you start​

To create a Project Access Token, you usually need Maintainer or Owner access to that GitLab project.

For Buzzbin, use these settings:

  • Role: Maintainer
  • Scopes: api and read_repository
  • Expiration date: set one deliberately and rotate before it expires

Token creation steps​

These steps follow the official GitLab flow:

  1. Open the target project in GitLab.
  2. In the left sidebar, go to Settings and then Access tokens.
  3. Select Add new token.
  4. In Token name, enter something clear such as Buzzbin Reviewer.
  5. If available, add a description like Repository review bot for Buzzbin.
  6. Set an Expiration date.
  7. Select the Maintainer role.
  8. Enable the api and read_repository scopes.
  9. Select Create project access token.

Right after creation​

GitLab only shows the full token value once. After you refresh or leave the page, you cannot view it again. So:

  • copy it immediately
  • keep it in a safe temporary place
  • paste it into the Buzzbin repository connection form right away

Why Maintainer is required​

Buzzbin does not only clone the repository. It also needs to register and manage the project webhook for the automatic review flow. GitLab restricts that webhook management capability below Maintainer, so a Developer token may still fail the connection even if the scopes look correct.

What this creates inside GitLab​

GitLab creates a bot user associated with the Project Access Token. That is why Buzzbin activity appears as a machine identity inside GitLab rather than as a human user's account.

If you cannot find the Access tokens page​

Check these likely causes:

  • your project role is not high enough
  • your GitLab instance restricts project access token creation
  • your GitLab plan or environment has subscription or quota limits

In that case, ask your GitLab administrator or project owner to create the token for you or grant the required access.

If the token expires or leaks​

Rotate or revoke it in GitLab and then update Buzzbin with the new token value. Once rotated, the old token stops working immediately.

Next step​

Go back to Connect a GitLab repository and finish the connection flow.