Adding users to the user table without "registering"

General
1

Hello,

Is it possible to add a user to the Users table such that

  1. the user isn’t consider “registered”,
  2. if the user were to register they would still get the built-in “use made registration” email,
  3. in my Users table the email address is the identity column and in my scenario i would have the email address. I wouldn’t have the email address so I could make the not required

Thanks,
Dan

2

Hi Dan,

Suppose a user is added to the Users table, would they still have to register with the registration API? If that’s the case, what is the purpose of preemptively adding users?

Btw, I could not quite understand the requirement #3 in your description.

Regards,
Mark

3

Hi Mark,

So the use case is that sometimes a user would register via my app “fresh”…meaning the user’s email address would not be in the Users table and would be added via the Register API. That’s perfect. However, sometimes a registered user might invite another new/unregistered user. My desire is to add the unregistered user to the Users table (so I could use that new User record in my app) but still allow the unregistered user register via my app and the Register API. I hope this makes sense. I know I could come up with another architecture but this would be the easiest.

I guess #3 was more of a comment.

BTW, do you work 24x7? :slight_smile:

Thanks,
Dan

4

Hi Dan,

It makes more sense now. One more question though: how would the invited user login? Does the system send some kind of auto-generated password?

Regards,
Mark
p.s. “Choose a Job You Love, and You Will Never Have To Work a Day in Your Life” ))

5

Ha. Love that.

I guess I was hoping there was away to add the user to the User table without having to create a dummy password such that the user could still register via the Register API.

If not maybe I should just create another “user” table (that has a one-to-one relationship to the Users table) for my database relationships and leave the Users table to provide authentication to my app. Thoughts?

Dan

6

I think that would be the best approach (create a separate table for invitations). This way it will be simpler to analyze the “conversion ratio” between the invited and those who ended up registering.

Regards,
Mark

7

Ok Mark. Thank for the advice. Have a great day.