Required permissions

Account

To log in to your account, GitProtect requires the following permissions:

1. Access the authenticated user’s API — GitProtect needs read and write access to the API, including:

   1. All groups and projects.

   2. The container registry.

   3. The package registry.

---

Personal Access Token (PAT)

GitLab can be integrated with GitProtect using a personal access token not only for a regular GitLab user account but also for a service account that is a member of the project. The access requirements are the same as for a regular user account; however, the service account must also have at least the maintainer role.

GitProtect supports legacy tokens; for proper system operation, it is recommended to use them instead of fine-grained tokens.

The following permissions are the minimum needed to register the GitProtect application in your account and access repositories:

• read_api

• read_repository

With minimal privileges, some metadata (such as issues) may not be included in the backup. Select the necessary permissions based on the data you need to protect—if you grant only read permissions, backups can be performed, but restoring data will require a new token or password with write permissions.

By creating a personal access token, you can assign different types of permissions. The following permissions allow you to back up the repository metadata in your organization:

• read_api — required to assign an organization to GitLab.

• api — grants full read/write access to the API, including all groups and projects.

• read_repository — required to access the list of repositories and perform backups.

• write_repository — required to restore a repository.

• read_registry — grants read access to Container Registry images when a project is private and authorization is required.

For more information about personal access tokens, visit the official GitLab website.