Setting up conditions on email registration Answered

Post author
Shadi null

Is there a way to ban emails from making new accounts on my memberstack app?
Let’s say they break ToA, I’d like to have a process that prevents them from registering again.
Also, is there a way to allow only business emails from registering? A condition like !=google.com etc?

Comments

10 comments

  • Comment author
    Julian Galluzzo

    It is your lucky day for point 2!
    https://www.memberstack.com/scripts/require-business-email-for-form-submission

    For point 1, what would the data points be? Do you have some domain block list?
    0
  • Comment author
    Shadi null

    Oh my goodness, you absolute legend!

    As for the people that break ToA, I'd likely have their domains/emails stored on some 'blacklist' DB (likely on airtable)

    0
  • Comment author
    Julian Galluzzo

    Would they be on a free plan? If so, I have an idea - if they're on a paid plan, I may need to rethink

    0
  • Comment author
    Shadi null

    I think I would want it to impact all plans, as there are certainly aspects where I need to keep a close eye on free users, there is also a risk that paying users may break ToA.
    So I would ideally like to have the possibility of adding them to a banned list, though I would also likely de-activate or end their account membership too if they broke ToA (meaning taking away their plan, if possible)

    0
  • Comment author
    Julian Galluzzo

    Actually I think it will work either way - what I'm thinking is this:

    1. Have your ban list in airtable
    2. Make a make.com scenario
    3. When a new member is created, it should reference this list. If the email domain is present in the blocklist, it should delete the member

    This is the automated version which would be good if you have this happening a LOT but it is also riskier, if this is an edge case, I would recommend instead having it send you an email or a slack message when it finds one of these members, and then you can delete them manually

    0
  • Comment author
    Shadi null

    OHHHHHH!!!!! I could also use that to prevent signups in theory, or to create extremely restrictive permissions on 1 plan, and assign it to people who match the blacklist crossreference during signup.
    Could pretty much be done in 3 modules! Love it! Thanks!

    0
  • Comment author
    Julian Galluzzo

    Yeah that could also work!! And no problem 🙌

    0
  • Comment author
    Shadi null

    Regarding memberscript 34, does this same functionality carry over for google/linkedin/github/etc auth signups?

    0
  • Comment author
    Julian Galluzzo

    ahhhhhhhhhh no it does not! I'll google to see if there is a solution for that

    I can't find anything simple for this one 🤔 I think the best thing to do would be some post-signup logic with make

    0
  • Comment author
    Shadi null

    I'll give that a look at (setting it up via make) once I've completed the page you just helped me on 😀

    0

Please sign in to leave a comment.