Add Custom Attribute to User Namespace when the Account is Blocked
Problem to solve
Unless a GitLab Administrator leaves an admin note with their username/id on a users' profile (admin view) we can't tell who blocked the account without looking through the logs. When a user reaches out because their account has been blocked Support is unable to tell why and by whom the account was blocked, which delays request to review/unblock the account. Additionally not having this data available in the application limits our ability to gather metrics regarding the volume and reason for accounts being blocked.
Intended users
- All GitLab Admins
- GitLab.com Trust and Safety
- GitLab.com Support
Proposal
If a GitLab Admin blocks an account, via the UI or API, the workflow kicked off in the background should include adding a Custom Attribute
to the User Namespace.
Suggested Custom Attribute:
Blocking
- Key =
blocked_by
- Value =
admin_username/id+date_time
Unblocking
- Key =
unblocked_by
- Value =
admin_username/id+date_time
Documentation on Custom Attributes:
- https://docs.gitlab.com/ee/api/custom_attributes.html
-
https://docs.gitlab.com/ee/api/users.html#for-admins (at the bottom of the
For Admins
Section)
Further details
Besides improving the user experience and Support process around unblock requests, it also helps with gathering metrics regarding this action.
Permissions and Security
This action can only be performed by a GitLab Admin
What does success look like, and how can we measure that?
Automatically adding a Custom Attribute
to a users profile when blocked stating who performed the action and at what date/time.