title: In a login system with 3 levels, what better way to create the tables in the database and login system?
body: <p>In a login system with 3 levels, what better way to create the tables in the database and login system?</p>
  
  <p>The three levels are: 'Client', 'Additional' and 'Administrator'.</p>
  
  <p>The 'Client' will access ALL your account details and you can register 'Additional'.
  The 'Additional' will have access to only a few details.
  The 'Administrator' can register new 'Clients'.</p>
  
  <p>1) Is it safe to have only one login url and let the system check the level of the user to then direct to the correct page?</p>
  
  <p>site. com/login
  If Additional OR Client will direct to -> site. com/client
  If Administrator will direct to site. com/admin</p>
  
  <p>2) Or the best way is to have a log file for the client and Additional site. com/client/login AND other to the Administrator site. com/admin/login</p>
  
  <p>3) I thought I'd create a table that contains only ID, Login, Password, and LEVEL of ALL users: Clients, Additional and Administrators, and making the query this table to see if the user exists, and what resources are available, then seek data in other tables, depending on the LEVEL, is this a safe practice?</p>
  
  <p>4) I also thought of doing the scan in 3 tables using INNER JOIN to see if the user has permission to access the system. And let ca level data in tables completely separate. It is an efficient alternative?</p>
  
  <p>Other ideas? Alternatives?</p>