Having two seperate `public` users table definitions?
Hey there! So my platform essentially has two different sides to it, there's the organization members who are paying to use the platform, and then the clients they invite to join their portal. So I'm exploring a switchup to my data model that would essentially haveto seperate tables in the
publicpublicauth.userspublic.userspublic.clientsauth.users
