[GH-ISSUE #316] [Feature]: Advanced Authentication via Email #200

New issue

Closed

opened 2026-05-07 00:07:34 +02:00 by BreizhHardware · 2 comments

BreizhHardware commented

2026-05-07 00:07:34 +02:00

Owner

Originally created by @cadtoolbox on GitHub (Feb 10, 2026).
Original GitHub issue: https://github.com/maziggy/bambuddy/issues/316

Originally assigned to: @cadtoolbox on GitHub.

Problem or Use Case

With the introduction of user authentication in Bambuddy, several key issues arise for a larger group of users using the application:

Admins needed to manually enter a new password for each new user. This would be tedious for a larger group of users and most likely default to laziness by the admin by giving them all the same "12345" password.
Current workflow for a user to reset their password starts with "Contact your Bambuddy administrator". This can cause significant delays in productivity if the Admin is unavailable for an extended duration.

Proposed Solution

The introduction of Advanced Authentication via Email would solve a few issues:

Set global SMTP settings to be used for general email communication and additional future enhancements.
Allows Admin to enter username and email address for the new user. The system would email the user the new secure and random password. No other user would know the password besides the new user. This is inherently more secure.
Password resets by the Admin would also be provided on a one-click basis. No manual entries required.
The user may now reset their own password if forgotten from the login screen.
Validates that the email address entered is correct as it's the only mechanism to receive the password.
Allows for notification message templates to be stored for the 'Welcome Email' and 'Password Reset'.
Can be enabled or disabled as an optional feature at any time.

Additional Bug Fixes:

Username/Email is not case sensitive for login.

Note: This branch is completed, tested and ready to go. I just need to create the Pull Request depending on how feedback goes.

Alternatives Considered

No response

Feature Category

Other

Priority

Critical for my use case

Mockups or Examples

Contribution

I would be willing to help implement this feature

Checklist

I have searched existing issues to ensure this feature hasn't already been requested

Originally created by @cadtoolbox on GitHub (Feb 10, 2026). Original GitHub issue: https://github.com/maziggy/bambuddy/issues/316 Originally assigned to: @cadtoolbox on GitHub. ### Problem or Use Case With the introduction of user authentication in Bambuddy, several key issues arise for a larger group of users using the application: - Admins needed to manually enter a new password for each new user. This would be tedious for a larger group of users and most likely default to laziness by the admin by giving them all the same "12345" password. - Current workflow for a user to reset their password starts with "Contact your Bambuddy administrator". This can cause significant delays in productivity if the Admin is unavailable for an extended duration. ### Proposed Solution The introduction of Advanced Authentication via Email would solve a few issues: - Set global SMTP settings to be used for general email communication and additional future enhancements. - Allows Admin to enter username and email address for the new user. The system would email the user the new secure and random password. No other user would know the password besides the new user. This is inherently more secure. - Password resets by the Admin would also be provided on a one-click basis. No manual entries required. - The user may now reset their own password if forgotten from the login screen. - Validates that the email address entered is correct as it's the only mechanism to receive the password. - Allows for notification message templates to be stored for the 'Welcome Email' and 'Password Reset'. - Can be enabled or disabled as an optional feature at any time. Additional Bug Fixes: - Username/Email is not case sensitive for login. ## **** Note: This branch is completed, tested and ready to go. I just need to create the Pull Request depending on how feedback goes. **** ### Alternatives Considered _No response_ ### Feature Category Other ### Priority Critical for my use case ### Mockups or Examples ![Image](https://github.com/user-attachments/assets/bb730477-007d-44be-a915-2db227afe829) ![Image](https://github.com/user-attachments/assets/d6fd6fa8-b404-404b-bf79-ee8fb19dded9) ![Image](https://github.com/user-attachments/assets/72b964f0-91ae-4284-a7b2-623e42a0f925) ![Image](https://github.com/user-attachments/assets/8cc1e853-39dd-47c8-bbe0-f37a93c28e8d) ![Image](https://github.com/user-attachments/assets/0f62adb4-0bac-46aa-b96d-5ef8971c2101) ### Contribution - [x] I would be willing to help implement this feature ### Checklist - [x] I have searched existing issues to ensure this feature hasn't already been requested