
I had an email interaction with someone asking about running our event. Based on what I learned in this, they should not sign up. They haven’t ever run an ultra before, so they don’t have an Ultrasignup account, so I can’t currently ban them from our event.
I wish I could ban them anyway, and in the future, when this person signs up for UltraSignup using the same email address, they won’t be able to register for our event until we remove them from the ban list.
Can you clarify what you’re intending to do with a feature like this? Are you wanting to permanently block a particular user from registering for your event, or are wanting to “vet” would-be registrants to ensure they have acknowledged particular experience or risks before allowing them to register? Or something different?

My intention was to use the USU Blacklist tool to prevent a particular user from registering. I’m looking at this again today, because after talking to race director about a situation, I want to make sure someone doesn’t sign up for our event. I can’t because I don’t have enough information about this person. I don’t know their DOB or email. I understand my original request to block an email address that doesn’t exist your system may not make sense, but I would like the ability to ban someone based on name.

That’s just wrong to ban someone based on their name. What if another user has the exact same name and qualifies to run your race? Instead, you should screen runners either based on your race description or a series of questions when they register.

For example, we intend a safe welcoming event for women, and as a result wouldn’t welcome a violent sexual abuser to our event. We don’t know the person’s email address to ban them, but USU knows their email address, so should be able to do the database linking for us.