I’m building an app where people can find tennis tournaments and register to them by creating their user in the app.
I want to add an option for the tournament’s admin to be able to add players themselves if needed.
What would be the best approach? I have thought of the following scenarios:
1. Admins can create users by entering their emails and register the created user to the tournament. The catch here is if that player one day wants to create a user, his email will be already in use and he’ll need to go through the password recovery process. It seems messy.
2. When the user registers to a tournament, it creates a “Player” thing with the User’s information. This way we’re not really registering the actual User, but making a copy of their info into another DT. So now admins can register a “Player” without the need to create a user.
This way is good if you want the player to have an account. To make it less messy, when they are added to the tournament I would email them explaining why they have been added and a button or link that let’s them reset their password. The only thing here is that link can expire so you would need to handle that on the reset password page.
This might work better for your scenario as it then means they could be added to multiple tournaments more easily. The only thing to keep in mind here is to setup the privacy rules correctly on the “Player” so that the emails aren’t exposed and then you can check if a users email matches the players emails in a backend workflow with ignore privacy rules checked.
Yes, I believe the second scenario is better. I also thought of adding a “User” field under the Player DT to have a direct connection between the two. Maybe this could make handling privacy rules a bit easier.
