Skip to content

Allow User Notes to Be Left on Users in the Gitpod Admin UI #10948

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jimmybrancaccio opened this issue Jun 27, 2022 · 3 comments
Open

Allow User Notes to Be Left on Users in the Gitpod Admin UI #10948

jimmybrancaccio opened this issue Jun 27, 2022 · 3 comments
Labels
feature: admin dashboard meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: feature request New feature or request

Comments

@jimmybrancaccio
Copy link

Is your feature request related to a problem? Please describe

When looking up reasons on why an account has marked as blocked it seems it can sometimes be found in Slack and other times not. Instead of whomever has blocked the account dropping a link into Slack I believe there would be more benefit to just keeping it all within the account in Gitpod.

This could likely be used for reason beyond just leaving notes on why a user was blocked as well, but any notes related the account.

Describe the behaviour you'd like

I would like to see that when the Block User button is clicked on a modal pops up and asks for the blocker to either select from a list of preset reasons or probably better require them to leave a note with the id of the workspace that caused the user to get blocked and what the reason was.

Describe alternatives you've considered

Right now, just hoping that whomever blocked the user also left a message in Slack with the workspace id and reason.

Additional context

N/A

@gtsiolis
Copy link
Contributor

gtsiolis commented Jun 27, 2022

Nice one! Thanks for opening this @jimmybrancaccio!

Thinking out loud, this could be implemented like the following:

  1. Once someone clicks on the block button, a confirmation modal is shown with a description text to allow someone to enter any reasons or links to internal discussions, etc.
  2. Additionally, we could also surface the user who performed this action for visibility.
  3. Once the user is blocked, an alert component containing the optional description text as well as the timestamp and the user who performed the action could be placed at the header of the user page.

Looping in @geropl and @jldec in case this is something we'd like to prioritize and work on designs before picking up for implementation.

@gtsiolis gtsiolis added type: feature request New feature or request feature: admin dashboard team: webapp Issue belongs to the WebApp team labels Jun 27, 2022
@stale
Copy link

stale bot commented Sep 26, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Sep 26, 2022
@gtsiolis gtsiolis added meta: never-stale This issue can never become stale and removed meta: stale This issue/PR is stale and will be closed soon labels Sep 26, 2022
@gtsiolis
Copy link
Contributor

Cross-posting for visibility relevant RFC for audit log for admin actions (internal). Cc @securitymirco @geropl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature: admin dashboard meta: never-stale This issue can never become stale team: webapp Issue belongs to the WebApp team type: feature request New feature or request
Projects
Status: No status
Development

No branches or pull requests

2 participants