Ability to edit user fields when approving a user signup

סיכום מבוסס בינה מלאכותית

Paul_King proposed a feature request to allow admins to edit specific user profile fields directly within the user signup approval dialog. Currently, administrators must approve a user, then navigate to their profile to manually adjust fields that determine access levels (e.g., public vs. private forum areas). Paul_King argues this multi-step process is inefficient and seeks the ability to nominate at least one profile field for direct editing during approval, while maintaining a “vanilla” setup to avoid breakage from Discourse updates.

Heliosurge suggested an alternative workflow using custom fields, groups, and staff notes to manage user access post-approval, though Paul_King acknowledged this requires too many steps [3]. Heliosurge also mentioned creating a custom theme component to inject fields into the review menu [4], but Paul_King remained hesitant due to potential instability during core updates [5].

Discourse staff member mcwumbly responded by acknowledging the complexity of designing an intuitive, configurable solution for all communities. He invited Paul_King and other users to provide more details on their specific use cases, such as which fields they need to edit and how many, to help inform future development. The discussion highlights the tension between advanced customization capabilities and the desire for stable, built-in administrative workflows.

Whenever a user signs up to my forum, I need to make a call as to what level of access to approve them for.

The current setup makes this more difficult than necessary.

I would really appreciate not having to approve them first, then to go back, reopen their user profile, and manually adjust the user profile status field that sets whether they see just the public forum area, or the private forum as well.

As an admin, I would like to be able to nominate at least one user profile field of my choice for inclusion and editing directly in the approval dialog.

5 לייקים

Have you considered using a custom Feild combined with Workflow(I might have this name wrong) with custom groups?

General idea you approve user, goto user profile and set a custom Feild that is only viewable by staff.

The Dropdown user custom Feild has say 2 options. The first being say called Probation and restricts new users to areas that user group can access. The Workflow then adds that user to Probation Group. This group can be set to not be public viewable. When the user has met your satisfactory conditions. You edit the user Feild to say Trusted Member. That adds them to the new group. Edit user groups and remove the user from Probation group

You can also use User Note as well for added staff communication and edit the user note.

The probation group also lets you find the probation users simply by viewing group membership. Make your staff that handle the new user approvals group owners as moderators only have access to groups they are apart of. Vs admin who have more free access.


I e thing I do with required approval on is check email domain to see if it is Disposable or not. If user email is disposable; I don’t approve and goto admin panel and add the domain to blocked domains.

If Self-hosted there is also a plugin that can be used. I

לייק 1

Thanks @Heliosurge I already have a process that works, and it is along the lines you describe, but it requires multiple steps/navigating of menus.

I see no intrinsic reason it should need multiple steps at all, if administrators could simply choose to include user fields directly in the approval dialog.

לייק 1

You’re quite welcome. If you have some experience with css, Java script and such. You could likely create a Theme component maybe to add the user Feild for the target user requiring approval in the Review Menu for new user approval.

I am still learning these things so a bit of a novice. I do see the benefits of your proposed idea to simply this. However I imagine a custom TC ATM is likely the best route.

What I am keen to avoid is creating anything that could break under successive Discourse updates – goal is to keep everything as vanilla as possible

2 לייקים

I can definitely appreciate where you’re coming from though for the most part I think a component in this idea here might be relatively safe. But yes there is always a risk that a change in core’s structure could cause breakage of the component.

Keeping an eye on upcoming changes may help as it provides often the needed info to keep a customization from breaking.

Even official or ones created by partners could experience breakage.

Yeah, it does take a little extra thought and care to design something that will work well for all communities.

Certainly configuration is a way out (make/allow admins configure what is shown in this dialog). But then we also need to think about how to design this in a way that is intuitive and discoverable for admins.

It’d help to get more input from you and others with this need. (I’m not sure who else needs this, but maybe we can find some hints of this need in past conversations here if we look).

In the meantime, any more detail you can share about your use case in particular would be helpful.

What’s the field you want to be able to edit? Would you want to be able to edit more than one? How have you implemented this part?