Ability to edit user fields when approving a user signup

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 Likes

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 Like

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 Like

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 Likes

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?

1 Like

Thanks @mcwumbly.

I run a forum for architects. In my case there are really only one or perhaps two custom user fields I would like to surface directly in the applicant approval dialog. The main one being ‘Forum Access Level’ - which is a dropdown field that dictates whether the applicant sees the private forum area or not (implemented by way of group memberships). Private forum users also see the public forum area.

I essentially need to satisfy myself that someone applying for private access really is an architect - I do this by matching the applicant’s name against the published list of registered architects in my country (New Zealand).

Occasionally non architects who want free advice etc from architects will sign up, and select ‘Private Forum’ despite not being eligible.
Since anyone is welcome to use the public forum, and since the private area is supposed to be where potentially sensitive issues are discussed and collegial support is offered, I will override that applicant’s setting to ‘Public Forum’ when approving them.
Conversely someone who is an architect but not familiar with the forum setup may mistakenly leave that setting on the ‘Public Forum’ default when applying, meaning I override to ‘Private Forum’, so they can use both areas.

The user fields I have are below.

I might occasionally want to correct other details that I know to be wrong while approving applications - the Professional Categories field is probably the main one; as it is sometimes not correctly filled in by applicants, being a multi-select and so not as intuitive to use for some.

I can certainly see a case where having a few fields would be useful to map to the

1 Like