Just continue with your current structure. You mainly want to separate front-end and back-end authorization. The models involved in each app are defined in the models to which the app belongs, and then the respective authorization mechanisms allow the front-end user model and the back-end user model to inherit AbstractBaseUser and write their own authorization methods. (Of course, you can also use other methods. You don’t have to inherit AbstractBaseUser. For example, if the front desk is an interface, you can use token authorization.) I have written a website before that requires student login, teacher login, and background login. That’s about it. Made.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Just continue with your current structure. You mainly want to separate front-end and back-end authorization. The models involved in each app are defined in the models to which the app belongs, and then the respective authorization mechanisms allow the front-end user model and the back-end user model to inherit AbstractBaseUser and write their own authorization methods. (Of course, you can also use other methods. You don’t have to inherit AbstractBaseUser. For example, if the front desk is an interface, you can use token authorization.) I have written a website before that requires student login, teacher login, and background login. That’s about it. Made.