hackclub / hackclub/hcb

[Admin] Require admins to provide reasons for locking users

Open
#12,931 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
870
Forks
138
Avg merge
1d 14h
Merged PRs (30d)
208

Description

Right now, we don't have any context within HCB about why a user was locked from signing into HCB. While an external Airtable base exists, it's possible to forget to add an entry when locking a user. We should require that admins add a note when they want to lock a user.

For simplicity, this should be an admin-only comment on the user.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the admin flow for locking a user's HCB sign-in and the existing user-comment behavior. Done means an admin cannot lock a user without providing a note, and that note is retained as an admin-only comment in HCB.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
authentication
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.