Current problem
Hi Fluxer team,
I'd like to report a significant usability gap in the admin experience regarding pending user registrations.
Currently, when someone registers on the instance and the registration mode is set to approval, the only indication that a new registration is waiting is:
a short sound, and
a small red indicator on the browser tab.
There is no persistent, visible notification inside the admin interface itself. If the admin is not actively looking at the browser tab, or has the sound muted, the pending registration can easily go unnoticed for hours or even days.
This becomes a real problem on instances where multiple users may register per day. Without a clear visual alert (e.g., a badge on the admin dashboard, a notification entry in an in-app notification center, or a dedicated "Pending Registrations" counter in the sidebar), administrators have no reliable way to know that action is required.
Suggested improvements:
A visible notification badge in the admin UI (e.g., on the "Users" or "Registration" section) showing the number of pending registrations.
An in-app notification entry that persists until the registration is reviewed.
Optionally, native browser push notifications or e-mail alerts (via the existing registration_alerts_webhook_url mechanism, but with a simpler setup).
Right now, relying only on a sound and a tab indicator is not sufficient for real-world instance administration.
Thank you for your work on Fluxer — I hope this can be addressed in a future release.
Best regards,
obergabe
Proposed change
Expected behaviour:
When a new user registers and the registration mode is set to approval, the administrator should receive a clear, persistent, and visible notification inside the admin interface — not just a short sound and a small indicator on the browser tab.
Specifically:
A visible badge or counter should appear in the admin UI (e.g., next to the "Users" or "Registration" section) showing the number of pending registrations.
The notification should persist until the administrator reviews or dismisses the pending registration.
Ideally, an in-app notification entry should be added to a notification center (if one exists), so the admin can see a history of pending registrations.
Optionally, support for browser push notifications or e-mail alerts (via the existing registration_alerts_webhook_url mechanism) would be a welcome addition, but the in-app badge should be the minimum requirement.
The goal is to ensure that instance administrators cannot miss a pending registration, even if they are not actively looking at the browser tab or have the sound muted.