GitLab Privilege in ZenTao

The GitLab privilege in ZenTao is consistent with GitLab (except in cases where the GitLab interface is not supported) in ZenTao 16.3.

This means that when a ZenTao user is bound to a GitLab user, that user will be controlled by both ZenTao system privileges and GitLab user privileges.

Privileges are clearer, more logical and more in line with management processes and specifications.

1. Check if the ZenTao user is bound to a GitLab user

• GitLab user binding check is only performed when the current user is not a ZenTao administrator;
• Assuming that the ZenTao user has been bound with the GitLab server user, the buttons in the GitLab server operation column can be clicked; 

• Assuming that the ZenTao user is not bound to the GitLab server user, the project list, group list, user list and user binding in the GitLab server operation column are all inoperable. 

2. Visible Privilege for GitLab Projects in ZenTao

• All GitLab projects are visible to ZenTao administrators.
• Assuming that the visibility of the GitLab project is public, the project is visible to any ZenTao users who have bound Gitlab users;
• Assuming that the GitLab project visibility is private and the current ZenTao user is bound to the GitLab user belonging to the project, the project is visible to the ZenTao user;
• Assuming that the GitLab project visibility is private and the current ZenTao user is bound to a GitLab user who does not belong to the project, the project is not visible to the ZenTao user;
• Assuming the GitLab project visibility is internal and the current ZenTao user is bound to a GitLab user within this GitLab server, the project is visible to the ZenTao user.

2.1 Edit GitLab project privilege in ZenTao

• ZenTao administrators are able to edit all GitLab projects;
• Assuming that the current ZenTao user is bound to the GitLab project owner user, the ZenTao user can edit this project;
• Assuming that the current ZenTao user is bound to the non-owner user of the GitLab project, the ZenTao user cannot edit this project;
• Projects cannot be edited through the GitLab interface maintainer, the same account can be edited in GitLab. 

2.2 Delete GitLab project privilege in ZenTao

• ZenTao administrators are able to delete all GitLab projects;
• Assuming that the current ZenTao user is bound to the owner user of the GitLab project, the ZenTao user can delete this item;
• Assuming that the current ZenTao user is bound to the non-owner user of the GitLab project, the ZenTao user cannot delete this item. 

2.3 Branch protection management privilege for GitLab projects in ZenTao

• ZenTao administrators can access the branch protection list;
• Assuming that the current ZenTao user is bound to the maintainer or owner user of the GitLab project, the ZenTao user can access the branch protection list;
• Assuming that the current ZenTao user is bound to the non-maintainer and non-owner users of the GitLab project, the ZenTao user cannot access the branch protection list.

2.4 Tag Protection management privilege for GitLab Projects in ZenTao

• ZenTao administrators can access the label protection list;
• Assuming that the current ZenTao user is bound to the maintainer or owner user of the GitLab project, the ZenTao user can access the tag protection list;
• Assuming that the current ZenTao user is bound to the non-maintainer and non-owner users of the GitLab project, the ZenTao user cannot access the tag protection list. 

3. Visible privilege for GitLab groups in ZenTao

The "Group List" in GitLab is not clickable and you cannot access the Group List page if the user is not bound to a GitLab user. Only if the ZenTao user is bound to the GitLab user can privileges be determined as follows:

• All GitLab groups are visible to ZenTao administrators;
• Assuming that the GitLab group visibility is public and the current ZenTao user is bound to the GitLab user, the group is visible to the ZenTao user;
• Assuming that the GitLab group visibility is private, and the current ZenTao user is bound to a GitLab user belonging to the group, the group is visible to the ZenTao user;
• Assuming that the GitLab group visibility is private, and the current ZenTao user is bound to a GitLab user who does not belong to the group, the group is not visible to the ZenTao user;
• Assuming that the GitLab group visibility is internal, and the current ZenTao user is bound to the GitLab user in the GitLab server, the group is visible to the ZenTao user.

3.1 Edit GitLab group privilege in ZenTao

• ZenTao administrators are able to edit all GitLab groups;
• Assuming that the current ZenTao user is bound to the GitLab project owner user, the ZenTao user can edit this group;
• Assuming that the current ZenTao user is bound to the non-owner user of the GitLab project, the ZenTao user cannot edit this group. 

3.2 Delete GitLab group privilege in ZenTao

• ZenTao administrators are able to delete all GitLab groups;
• Assuming that the current ZenTao user is bound to the GitLab project owner user, the ZenTao user can delete this group;
• Assuming that the current ZenTao user is bound to the non-owner user of the GitLab project, the ZenTao user cannot delete this group. 

4. GitLab merge request data display privilege in ZenTao

• ZenTao administrators can view all merge request data;
• Non-ZenTao administrator accounts can only view the merge request information of the GitLab user bound to this ZenTao user, and this user is a non-guest role in the GitLab project.

4.1 Privileges when creating GitLab merge requests in ZenTao

• ZenTao users can only select the server bound to the GitLab user when creating a merge request:

ZenTao administrators can select all GitLab servers when creating a merge request

If the current user is not a ZenTao administrator and has been bound with a GitLab user, the user can only select the GitLab server with access privilege on the Create Merge Request page

• ZenTao users can only select GitLab projects that they have access to when creating a merge request:

ZenTao administrators can select all GitLab projects under this GitLab server when creating a merge request

If the current user is not a Zendao administrator and is bound to a GitLab user, only GitLab projects that this GitLab user has developer/maintainer/owner Edit GitLab merge request permission can be selected on the Create Merge Request page

4.2 Edit GitLab merge request privilege in ZenTao

• ZenTao administrators can edit all GitLab projects;
• Assuming the current ZenTao user is bound to the developer/maintainer/owner user of the GitLab project, the ZenTao user can edit this merge request;
• Assuming that the current ZenTao user is bound to a non-developer, non-maintainer, and non-owner user of the GitLab project, the ZenTao user cannot edit this merge request. 

4.3 Delete GitLab merge request privilege in ZenTao

• ZenTao administrators can delete all GitLab merge requests;
• Assuming that the current ZenTao user is bound to the owner user of the GitLab project, the ZenTao user can delete the merge request under the project;
• Assuming that the current ZenTao user is bound to the non-owner user of the GitLab project, the ZenTao user cannot delete the merge request under the project.