You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we are keeping email address in the user table, and the user table is readable by all... we need to make sure that the email is private.
I suggest having an accounts_private table which is created and cascading with accounts table which holds all personal information we wouldnt want to be shared. This can then have RLS to be read/write only by the client.
NOTE: This will break a lot of things. So we need to make sure that we test everything. Some of the postgres functions might reference the accounts table values that would be moved to private. I highly recommend using ChatGPT and asking it to modify these for you unless you really know the SQL :)
The text was updated successfully, but these errors were encountered:
Right now we are keeping email address in the user table, and the user table is readable by all... we need to make sure that the email is private.
I suggest having an accounts_private table which is created and cascading with accounts table which holds all personal information we wouldnt want to be shared. This can then have RLS to be read/write only by the client.
NOTE: This will break a lot of things. So we need to make sure that we test everything. Some of the postgres functions might reference the accounts table values that would be moved to private. I highly recommend using ChatGPT and asking it to modify these for you unless you really know the SQL :)
The text was updated successfully, but these errors were encountered: