Do you know the difference between the three project permissions of GitLab?

Preface

When we create a new project on GitLab, we all choose a visibility permission for the project. There are three visibility permissions for GitLab: Private, Internal, and Public. The difference between these three permissions is described below.

Authority

Public

You can clone public projects without any authentication.

They will also be listed on the public access directory (/public).

Any logged-in user will have guest permissions for the project.

Both people who log in to GitLab for public projects can see the project and can clone and download it, which is equivalent to making it public.

Internal

Any logged-in user can clone internal projects.

They will also be listed in the public access directory (/public) of the logged in user.

Any logged-in user will have guest permissions for the project.

For internal projects, only users who log in to GitLab can see the project and clone, and users who are not logged in cannot see the project.

Private project (private)

Only the creator and project team members can access

After the private project is created, only the creator can access it at first, but other users cannot access it (that is, the project cannot be seen). Only when the creator or authorized group member adds the user as a group member of the project, the user will see and access the project, which has better privacy.

The following describes how to add project team members

Add group members

Add group members in the Members option of project Settings

Parameter Description:

Select members to invite: select users, click on a drop-down box to select users

Choose a role permission: Choose a role permission for the user

Access expiration date: expiration date