Ability to Give a reason for Denying a User Access Request

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

Problem to solve

When denying a user access request to a group or project, it is important to be able to send a one line message on the reason. This is most important for community relations when it is necessary to deny access to projects for which higher access levels would expose sensitive information.

It is also helpful for redirections like "Please request this access at a sub-group or project level."

Intended users

Further details

A denial is disappointing to the receiver - but even more so when there is no reason given. GitLab does not have another convenient way to communicate this information.

However, even if it did:

  • the information is much more likely to be provided if a prompt upon deny was provided and simply sent with the denial email.
  • It also makes more sense for the denial to have the information so the end user is immediately aware of the reason along with the action rather than having to find it in another communication channel (along with the risk it is not received in the other channel)

Proposal

When I click the Delete icon for a user access request, prompt for a reason string and include it in the outbound email. Allow ample characters for explanatory text and urls to be sent.

What does success look like, and how can we measure that?

The user who is denied receives a reason for the denial at the same time as learning of the denial.

What is the type of buyer?

Everyone

Is this a cross-stage feature?

No.

Links / references

Edited by 🤖 GitLab Bot 🤖