GitLab API Token

Read-only access to GitLab repositories is required for Enji to provide analytics and insights. Depending on the setup, one of the following token types can be used:

• Personal Access Token — tied to a user
• Project Access Token — tied to a specific repository
• Group Access Token — tied to a group and all its projects

These instructions apply to both GitLab Cloud and GitLab Self-Managed.

Best for: small teams or individual repositories where user-level access is acceptable.

1. Log in to your GitLab account.

2. Go to User Settings → Access Tokens.
For GitLab Cloud: https://gitlab.com/-/profile/personal_access_tokens
For GitLab Self-Managed: https:///-/profile/personal_access_tokens

3. Fill out the form:

Name: Enji Read Token

Expiration Date: a year or more

Scopes (check all of these):

☑️ read_repository

☑️ read_api

☑️ read_user

☑️ read_registry

☑️ read_package_registry

4. Click Create personal access token

5. Copy and securely store the token — it won't be shown again.

Best for: giving access to a single repository only.

1. Open the target GitLab project.

2. Go to Settings → Access Tokens.

3. Fill out the form:

Name: Enji Read Token

Role: Reporter

Scopes:

☑️ read_repository

☑️ read_api

☑️ read_registry

☑️ read_package_registry

4. Click Create project access token

5. Copy and securely store the token.

Best for: giving access to all repositories inside a group.

1. Navigate to your GitLab Group.

2. Go to Settings → Access Tokens.

3. Fill out the form:

Name: Enji Read Token

Role: Reporter

Scopes:

☑️ read_repository

☑️ read_api

☑️ read_registry

☑️ read_package_registry

4. Click Create group access token

5. Copy and securely store the token.

➡️ You can revoke any token at any time.

➡️ Do not enable write-level scopes (write_repository, api, sudo) — Enji only needs to read data.

➡️ For GitLab Self-Managed, make sure Access Token functionality is enabled in the admin settings.