Send admin notification only after user verifies email
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ruby
- Domain
- authentication, backend
Research direction
Trace the signup flow, email-verification flow, and existing administrator notification entry point. Determine where the user becomes verified and how notification timing could be configured while preserving current behavior. Done means unverified users cause no notification, verified users do, and both timing options work as documented.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem?
Yes.
Currently, when a new user signs up, Greenlight can send administrators an email notification such as:
New BigBlueButton User Signup
However, this notification is sent immediately after registration, before the user verifies their email address.
This creates unnecessary notifications when someone enters a non-existing or fake email address from an allowed domain. Such users remain in the Unverified state, but administrators still receive a signup notification.
In installations with domain-restricted registration, this can generate a lot of noise.
Proposed solution
Add an option to notify administrators only after the user successfully verifies their email address.
For example, instead of sending the admin notification on user creation:
signup -> admin notification
it should optionally work like this:
signup -> email verification -> verified=true -> admin notification
The existing behavior could remain available as one option.
Possible settings could be:
- Notify admins when a user signs up
- Notify admins when a user verifies their email
or alternatively:
- Admin signup notification timing:
- Immediately after signup
- After email verification
Expected behavior
- User registers.
- User is created as
Unverified. - No admin notification is sent yet.
- User clicks the verification link.
- User becomes
verified=true. - Administrators receive the new user notification.
Users who never verify their email should not trigger an admin notification.
Why this is useful
This would reduce unnecessary admin emails caused by fake, mistyped, or non-existent addresses while still notifying administrators about real users who completed registration.
It would be especially useful for installations where registration is restricted to specific email domains.
- Dominant language
- Ruby
- Stars
- 850
- Forks
- 3.6k
- Avg merge
- 9d 9h
- Merged PRs (30d)
- 9
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bigbluebutton/greenlight
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
bigbluebutton/greenlight#6266 ·
Maintainers usually reply within 6 days
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
bigbluebutton/greenlight#6359 ·
Maintainers usually reply within 6 days
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
bigbluebutton/greenlight#6340 ·
Maintainers usually reply within 6 days
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
bigbluebutton/greenlight#6338 ·
Maintainers usually reply within 6 days
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
bigbluebutton/greenlight#6326 · 1 reaction ·
Maintainers usually reply within 6 days
All issues in bigbluebutton/greenlight
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 72/100
Parallels/vagrant-parallels#530 ·
-
Good first issue: add rails-hotwire stack budget preset (Ruby on Rails 8 + Hotwire + PostgreSQL)Openenhancement good first issue help wanted
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
simp/pupmod-simp-tftpboot#152 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
fluent/fluent-plugin-kafka#612 ·
Maintainers usually reply within 2 days