debian-mirror-gitlab/doc/user/project/settings/project_access_tokens.md

stage	group	info	type
Manage	Authentication and Authorization	To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments	reference, howto

Project access tokens

• Introduced in GitLab 13.0.
• Became available on GitLab.com in GitLab 13.5 for paid groups only.
• Feature flag removed in GitLab 13.5.
• Changed in GitLab 14.5. Default prefix added.

Project access tokens are similar to passwords, except you can limit access to resources, select a limited role, and provide an expiry date.

Use a project access token to authenticate:

• With the GitLab API.
• With Git, when using HTTP Basic Authentication, use:
  • Any non-blank value as a username.
  • The project access token as the password.

Project access tokens are similar to group access tokens and personal access tokens.

In self-managed instances, project access tokens are subject to the same maximum lifetime limits as personal access tokens if the limit is set.

WARNING: The ability to create project access tokens without expiry was deprecated in GitLab 15.4 and is planned for removal in GitLab 16.0. When this ability is removed, existing project access tokens without an expiry are planned to have an expiry added. The automatic adding of an expiry occurs on GitLab.com during the 16.0 milestone. The automatic adding of an expiry occurs on self-managed instances when they are upgraded to GitLab 16.0. This change is a breaking change.

You can use project access tokens:

• On GitLab SaaS if you have the Premium license tier or higher. Project access tokens are not available with a trial license.
• On self-managed instances of GitLab, with any license tier. If you have the Free tier:
  • Review your security and compliance policies around user self-enrollment.
  • Consider disabling project access tokens to lower potential abuse.

You cannot use project access tokens to create other group, project, or personal access tokens.

Project access tokens inherit the default prefix setting configured for personal access tokens.

NOTE: Project access tokens are not FIPS compliant and creation and use are disabled when FIPS mode is enabled.

Create a project access token

• Introduced in GitLab 15.1, Owners can select Owner role for project access tokens.
• Introduced in GitLab 15.3, default expiration of 30 days and default role of Guest is populated in the UI.

To create a project access token:

1. On the top bar, select Main menu > Projects and find your project.

2. On the left sidebar, select Settings > Access Tokens.

3. Enter a name. The token name is visible to any user with permissions to view the project.

4. Optional. Enter an expiry date for the token. The token expires on that date at midnight UTC. An instance-wide maximum lifetime setting can limit the maximum allowable lifetime in self-managed instances.

5. Select a role for the token.

6. Select the desired scopes.

7. Select Create project access token.

A project access token is displayed. Save the project access token somewhere safe. After you leave or refresh the page, you can't view it again.

Revoke a project access token

To revoke a project access token:

1. On the top bar, select Main menu > Projects and find your project.
2. On the left sidebar, select Settings > Access Tokens.
3. Next to the project access token to revoke, select Revoke.

Scopes for a project access token

The scope determines the actions you can perform when you authenticate with a project access token.

Scope	Description
api	Grants complete read and write access to the scoped project API, including the Package Registry.
read_api	Grants read access to the scoped project API, including the Package Registry.
read_registry	Grants read access (pull) to the Container Registry images if a project is private and authorization is required.
write_registry	Grants write access (push) to the Container Registry.
read_repository	Grants read access (pull) to the repository.
write_repository	Grants read and write access (pull and push) to the repository.

Enable or disable project access token creation

Introduced in GitLab 13.11.

To enable or disable project access token creation for all projects in a top-level group:

1. On the top bar, select Main menu > Groups and find your group.
2. On the left sidebar, select Settings > General.
3. Expand Permissions and group features.
4. Under Permissions, turn on or off Allow project and group access token creation.

Even when creation is disabled, you can still use and revoke existing project access tokens.

Bot users for projects

• Introduced in GitLab 13.0.
• Excluded from license seat use in GitLab 13.5.

Bot users for projects are GitLab-created service accounts. Each time you create a project access token, a bot user is created and added to the project. These bot users do not count as licensed seats.

The bot users for projects have permissions that correspond with the selected role and scope of the project access token.

• The name is set to the name of the token.
• The username is set to project_{project_id}_bot for the first access token. For example, project_123_bot.
• The email is set to project{project_id}_bot@noreply.{Gitlab.config.gitlab.host}. For example, project123_bot@noreply.example.com.
• For additional access tokens in the same project, the username is set to project_{project_id}_bot{bot_count}. For example, project_123_bot1.
• For additional access tokens in the same project, the email is set to project{project_id}_bot{bot_count}@noreply.{Gitlab.config.gitlab.host}. For example, project123_bot1@noreply.example.com.

API calls made with a project access token are associated with the corresponding bot user.

Bot users for projects:

• Are included in a project's member list but cannot be modified.
• Cannot be added to any other project.
• Can have a maximum role of Owner for a project. For more information, see Create a project access token.

When the project access token is revoked:

• The bot user is deleted.
• All records are moved to a system-wide user with the username Ghost User.

See also Bot users for groups.