Skip to content

Make contributions of blocked users visible to non-admin users

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Proposal

The activities of a user who has been blocked from Gitlab (such as when Gitlab is using LDAP for authentication and the LDAP user has been deactivated) ought to be viewable without admin permissions. It doesn't make sense that a project owner can make any changes they wish to a project, but cannot view changes that another user has made to their project if that user account has been blocked. As a regular user, I can view the contribution history of any other user without special permissions - I don't understand why this history becomes hidden when a user is deactivated.

There are lots of obvious reasons why you might want to review a user's activity after their account has been blocked. Perhaps the user was blocked due to malicious activity, and project owners may want to review contributions by that user. Perhaps a contractor's contributions need to be reviewed to see whether the contractor should be renewed, etc.

Currently, Gitlab administrators are able to see this activity, but not any other permission level. Granting someone read-only access to the history of a blocked user should not require making them an administrator over the whole installation.

The history should either not be hidden when a user is blocked, or a new read permission level should be added which allows designated users to review this history.

Edited by 🤖 GitLab Bot 🤖