We screen all registrations unless the email address supplied is from a recognizable university or company or we know the person involved. Part of that screening process involves sending an email requesting information on the applicant’s particular interest in the community and any related outputs. We also share this review workload among three admins.
The following feature would therefore assist this screening process and reduce confusion:
a way of noting which particular admin is processing a given application — probably just a “this is mine” button to hit
And to continue with the wish‑list:
some way of logging progress via text input would be additionally useful
Also, you might include the info that you want in user custom fields that are required when they open the account. You coyly also use a custom field that was staff only that you could use to mark who is processing.
I think you can also use their email address to add them to a group that could help automate things.
By the way, I highlight and copy three lines of the displayed pending user fields, paste this into the emacs editor, and then run some lisp scripting to generate an outgoing email. I am not suggesting this functionality gets built into discourse — it’s just my work around to save some error‑prone typing. R
I too use the One True Editor. I’ve started using VS Code for the bulk of my Discourse plugin/theme development, but Emacs is always open. And just now I had to pull stuff into Emacs to solve an issue using a keyboard macro, which I don’t think exists in VSCode and don’t see how anyone lives without it.
Well, it would be a bit more trouble to develop than your Lisp script was, but it could be done in a plugin!
You can do that right now with the existing features in core, so that covers.
The other piece you want is
For this you could use either user notes as suggested above, or another custom user field where you could just type in whatever you wanted. Or, if the process is predictable, you could have another dropdown with stuff like
contacted user/waiting for reply
So I think that might be all you need and you can recategorize as #support?