Question

I’m designing a database for our CRM system and need some help with the CRM User table.

Types of users:

1. Admin
2. Sales Reps from Branch 2
3. Sales Reps from Branch 3
4. Client login

Now for this scenario would it make sense to have all users in a single table and have a table attribute called “type” to identify the type of user? OR should I have a seperate table for each type of user? Also, there will be some information sharing between the Sales reps.

Answer 1

Typically, I usually go with one User table with a Type associated with it. If you have additional Sales Rep attributes you want to store, create a SalesRep table with a foreign key back to the User table. Then, create a view that joins User and SalesRep, so it looks, logically, like there’s just a usvSalesRep table that has all of the attributes you need for Sales Reps.

But, this depends a lot on data volume and transaction load, so additional information you can supply there is useful.