Database Design for User Authentication in Two-Sided Business
In this meeting, the State Changer discusses their dilemma regarding database design for their project. They initially thought of having client access control for internal users and authenticating external facing users (patients). However, they are now considering creating a separate user's table for authentication endpoints. They seek clarification on whether this setup would work, with authentication data in the users table and a reference in the patient's table. The State Changer is advised that there are two possible approaches: a centralized users table for both patient and doctor logins or two separate authentication regimes for each type of user. The built-in Xano authentication regime is mentioned, with the option to create custom authentication for both or one type of user. The State Changer also mentions the possibility of using Google authentication for doctors in the future. They express excitement to learn from other questions in the meeting.