title: Make a table for every user that signs up (Is it practical?)
body: <p>I'm working on a authentication system for my C# apps, the authentication system is in PHP. It has users and it works perfectly right now for one person, such as myself. I can add my own customers, set their permissions, update my program, and do much more.</p>
  
  <p>But...</p>
  
  <p>I want it to work so that I can have users sign up with a developer account from which they can control their own customers. But the problem is, with just my account I already have three tables. (customers, files, and global)</p>
  
  <p>So should I make a whole new table for every customer? Or should I just shove them all in one huge table, with a column stating the ID of their parent developer.</p>
  
  <p>I really hope this was clear enough...</p>
  
  <p>If you're still confused here's some pics which may help
  (This is the three tables I need for just my developer account)</p>
  
  <p><img src="https://i.stack.imgur.com/IyTgU.png" alt=""></p>
  
  <hr>
  
  <p><img src="https://i.stack.imgur.com/hfkmz.png" alt=""></p>
  
  <hr>
  
  <p><img src="https://i.stack.imgur.com/2W1pZ.png" alt=""></p>
  
  <p>(Don't worry these are not my actual users passwords... I'm still working on the website, it's all example stuff now)</p>