We have had numerous clients request that the designated role(s) be added to matched users when a batch of e-mail addresses (sometimes a few thousand) are added to the pre-approved list.

Currently, if you add an e-mail, say foo@bar.com to have the role "member" but the user has already registered on the site, the module throws an error and requires the user to sift through the (sometimes very long) list to find and remove any subscribers already registered.

Many of our clients are membership associations, and they will dump a member list into the register pre-approved box. Often, those seeking membership privileges have already registered on the site.

I recognize this is a "pre-registration" module by design, however, it has the potential to manage roles by domain and serve many other useful functions. Offering a setting to users to add the roles to the users/domains that already exist on the site would be very helpful.

Imagine if you were an organization that allowed various companies to have member access by domain name, but the domains were updated each year. You could simply use the bulk operations module to clear the member role from all users on the site, then drop in a new list of the approved domains into the register pre-approved module and poof -- all users from the pre-approved domains would be members, and the others would not.

Let me know if I may clarify or contribute in any way. Thanks!

Comments

johnhanley’s picture

johnhanley commented

It's an interesting idea.

As you said, the module was originally intended to assign a role (or roles) at the time of registration. However, what you're suggesting might be a reasonable way to handle existing users. Basically, the role assignment happening at registration could take place when adding email addresses. Automatically assigning roles by domain is different though and would require a separate loop per domain.

johnhanley’s picture

johnhanley commented

I've been giving this feature request some additional thought and believe it could be integrated quite nicely. The idea would be to provide 2 checkboxes when adding new patterns: one for assigning a role (or roles) to existing individual email addresses and another for existing email addresses matching a domain name. The latter would create a little overhead (depending on the number of patterns and user accounts), but it's only executed deliberately and incidentally so the impact would be minimal and momentary.

My main problem is time. I'm currently swamped with professional obligations and can't promise when I'll have the bandwidth. That said, I could make it a higher priority if you're willing to sponsor the feature request. Send me a PM if you're interested.

johnhanley’s picture

johnhanley commented
Status: Active » Postponed
johnhanley’s picture

johnhanley commented
Status: Postponed » Closed (duplicate)

Please see related issue #2394829.