jkersu

Cool, thanks for the advice 🙂

(2) (1) 👨‍🎓 (1) (1)
jkersu

Yep that sounds cleaner. Thanks. Probably will add a check to see if the Member is an Admin as well as in my particular case they dont belong to an account

wmk

LoginHandler has an extension point "afterLogin". There you can check if the member has the account object set

(1)
jkersu

Probably don’t want to delete them… there was a case in the past where we had that functionality and the CMS user accidentally pressed unpublish on the Account. Bye bye users 😛

andante

you could also do something like add them to the "deactivated" group and add logic to not allow members in that group to log in

jkersu

I’m assuming that I’ll have to add the logic to the authenticator/login handler then with this way?

andante

yeah - well basically you'd let them log in, and then redirect them to some sort of "sorry, your account has been deactivated" static page

jkersu

Yep, the kind of member can only belong to 1 account

wmk

Does that kind of member have a special group? If yes, you could check if the member belongs to a valid account object

andante

if you don't ever expect them to log in again, just delete them