Clerk profile

Hello, sorry if this is a dumb question but I don't know Clerk very well and I would like to understand how it works. Is it useful to have a Profile table if we want more information for the user (for example his shoe size)? And should we use the userId in our database as if we had a user table and then call getUser from the clerk client?

Thanks

MeyerOP•5/13/23, 10:27 PM

At the same time, how do you have to enter this information ( not optional ) when creating an account?

m$•5/14/23, 1:45 AM

Believe you need to look into webhooks for clerk @Meyer

Mm$Believe you need to look into webhooks for clerk @Meyer

MeyerOP•5/14/23, 3:20 AM

thanks, I will look at

Kairu•5/14/23, 9:39 AM

you could use the metadata field to store small pieces of information

Kairu•5/14/23, 9:39 AM

im not sure if the 8kb limit is application-wide or per user though

Kairu•5/14/23, 9:39 AM

i'm using it to store an admin boolean instead of hardcoding email domains into the app or building out an acl system

KKairu you could use the metadata field to store small pieces of information

MeyerOP•5/14/23, 5:41 PM

Hello, yes i use metadata but i dont found built in soluce for adding required metadata. I will try to add a webhook when sign up add all metadata required.

zsrobinson•5/15/23, 1:12 PM

I've heard that it's not a bad idea to have your own users table, and map the clerk user IDs to your own ids that you can use throughout the rest of your database (I think I saw theo mention this on twitter, though I wouldn't be able to find the tweet)

zsrobinson•5/15/23, 1:12 PM

It just makes it easier to transition to another auth provider if needed, as well as storing that extra data you have in another column of that table

Clerk profile

Similar Threads

Similar Threads

Similar Threads