Question About Safely Modifying the auth.users Table in Supabase
Hi everyone,
I have a question regarding the auth.users table in Supabase. I’m considering adding a new column, has_access, to this table. The idea is to use this column to check during login whether a user is allowed to access the site or not.
Before proceeding, I want to ensure that this approach is safe. Specifically:
1. Could adding a custom column to the auth.users table disrupt its internal structure or functionality?
2. Are there any potential risks or best practices I should be aware of when modifying this system table?
I’d appreciate any advice or insights from those who have worked with Supabase or similar systems. Thanks in advance!
I have a question regarding the auth.users table in Supabase. I’m considering adding a new column, has_access, to this table. The idea is to use this column to check during login whether a user is allowed to access the site or not.
Before proceeding, I want to ensure that this approach is safe. Specifically:
1. Could adding a custom column to the auth.users table disrupt its internal structure or functionality?
2. Are there any potential risks or best practices I should be aware of when modifying this system table?
I’d appreciate any advice or insights from those who have worked with Supabase or similar systems. Thanks in advance!
