[eluser]JulianM[/eluser]
Hi theshiftexchange, thank you for your response.
I am in progress of design the database, my concern is that I am new using DX Auth and probably this situation happened before (I have used other auth libraries before).
DX Auth has a users table that fits ok for me. It do not have first_name nor last_name and that makes sense for me (since these fields are more like user_profile and not user itself). It only have the user required fields such as username, email, last_login, etc.
Moreover, user_profile table has the other fields (firstname, lastname, city, etc.)
So, if I should have normal Users (instead of Admin or Supervisors) I may use user_profile for store the user data, just as DX Auth examples do.
In my case, I have Admin and Supervisor, not Users (each entity with different fields), so I thought in using a similar approach (instead of user_profile, having supervisor_profile and admin_profile).
I still want to use the libraries facilities, that is my big concern (I don't want to re-invent the wheel).
Any with previous experience on DX Auth seems this approach makes sense?
Thanks.
Julian
[quote author="theshiftexchange" date="1242383052"]Hmmm... to be sounds like you need to re-design your database.
You should have "users" with first/last names etc.
The users can be either Admins or Supervisors or general users
You can then have another table of user ids, supervisors, and link that with companies.[/quote]