Registration of users that already have a record in DB (while onboarding) #1416
Replies: 1 comment 1 reply
-
|
That's a very specific feature, and will greatly depends on what you want to achieve. The solution you describe seems to be the most versatile, but probably the most complex. Regarding step 3, in terms of implementation, it'll look like the Another solution I can see is to store everything in session data: you don't create any object in your database until the account is created. Then, when the user upgrades, you create both the User record and all the other objects directly linked to it. The advantage with this approach is that you don't end up with "ghost" objects in your DB associated with temporary users that never upgraded their account. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
In my app, I want to allow visitors to try a few functionalities of the app before creating an account. At some point in the process they will be asked to create an account if they want to store their progress.
To achieve this, I need to create a new User record when someone starts this process, so their activity can be retained on their profile if they decide to create an account. Is this possible to do with fastapi-users? Any ideas on how to implement this? Here is what I'm thinking of:
But I'm not sure what would be the best way to implement the step 3, specially with oauth. Any help on this is appreciated.
Beta Was this translation helpful? Give feedback.
All reactions