https://supabase.com/ logo
Join Discord
Powered by
Is it possible to find the `user_metadata` somewhe...
# help
d
Is it possible to find the 
user_metadata
somewhere in the supabase Authentification? All I can find is email/phone/provider/created/last sign in/user UID
n
Hello @daviscup! This thread has been automatically created from your message in #843999948717555735 a few seconds ago. We have already mentioned the @User so that they can see your message and help you as soon as possible! Want to unsubscribe from this thread? Right-click the thread in Discord (or use the ``...`` menu) and select "Leave Thread" to unsubscribe from future updates. Want to change the title? Use the ``/title`` command! We have solved your problem? Click the button below to archive it.
g
Can you be more specific on "somewhere in the supabase Authentification"? That is very unclear.
d
I was only checking the Authentication tab, not the table editor/schema auth . Thank you very much
I have one more quick question.
I've been reading the auth-update documentation and I'm not sure about the wording. Maybe you can help me out here. 
User metadata: It's generally better to store user data in a table inside your public schema (i.e. public.users). Use the update() method if you have data which rarely changes or is specific only to the logged in user.
Would this include things like user avatars/ addresses/ language preferences etc.? I'm not sure if I should store that in the user's metadata or in a seperate public db. @garyaustin sorry for the ping in case that's inappropriate
m
@daviscup for my use i put in auth table only private data who are never use by my function or other users. because it's hard to access it, i put in public.users avatars/ addresses/ language preferences. since all of them will be use by other than the user .
just if you will use in emailing it's better to do it in public.users for me
g
Also putting generic user info that you don't need for RLS type stuff increases the size of every jwt token (metadata is part of jwt). And user metatdata is not secure and can be changed by client code.
d
great info. thanks guys!
PreviousNext
Powered by