Skip to main content

It would be helpful to have some automated ways -- via system emails -- to retarget users that have signed up for the community but not yet confirmed their email. While this is a small number, it’s a repetitive maintenance task for CMs. For example, today I have to manually go into Control > Users - filter by their role, then send a private message or reach out over email to get them active (or even manually change them to registered).

And yes, I could do this all with APIs -- but not everyone has access to the engineering teams to support those efforts.

@Scott Baldwin thanks for your idea. How would you see this working? What would you expect to happen if an user has not signed up to the community after a while.

Updated idea status New → Open

@Marion Frecaut 

I hate to jump to solutions, but some thoughts:

  • after X days (1-5 days maybe?) send a system email to notify that their account has not yet been activated
  • repeat the same X times (maybe 2x more) then mark account as inactive (would have to be a new primary role created)

It would also be helpful to know if these emails are bouncing back as undelivered so account could just be banned or deleted. 

I used to do this manually on a weekly basis. Export all the new users, sort by roles.not-activated, and them email those members to see if they wanted me to confirm their accounts on the backend - since the token would probably be expired by then. 

Yep, that’s what I do today @Kgastaldo -- was just looking for some way to automate.

I’d like that too. Voting!

I’m voting for this as well, tired of taking 10 steps to get people to validate ;) 

Terms & ConditionsCookie settingsAccessibility statement