So i am currently making a CRM ticketing system for my school project. It will be having 3 main entities- CLIENT, EMPLOYEE and ADMIN interacting with the system. The client can create tickets which can be worked on by employees who can be assigned to it by the admins.

What is a better practice to follow for creating the schemas for the 3 entities as some of the information will be similar like name, email, password, etc. should i make one single schema model for users and assign roles or will it be better to create 3 different schemas for Client, Employee and Admin. Main issue to be faced for creating single schema would be managing it on the front-end using react. If i use 3 different schemas i can easily create separate private routes on the front end using react routes

CodePudding user response：

It would be better to use 3 different schemas, so your data will not be messed up in db and frontend page.