This website / pseudo-application is going to be meant for a senate of an organization, so when I refer to "member", I'm actually referring to "senate member". I fear this probably helps in understanding what I'm trying to do here.
So with that being said, I thought it would be preferable to have a table for "senate members" and then another for "users" in that the user is someone who manages the members--equivalent to your basic admin, etc. After thinking this over, I began to believe that I should just have 1 single table for everyone and simply include the respective fields for authentication or admin-like capabilities. It made me second-guess myself, though, because of the other fields that would be in this same table, such as "office phone number", "room number", "department", and other profile-like information. Is it okay to have that sort of information all in 1 table like this??? Does it break any pertinent MySQL laws?
Sorry for the confusion, too, btw.