The documentation provides some ways to extend the functionality of the user model But the thing I didn't know at first was that once you have your application working and all, it's quite difficult to make changes to the user model. So I always prefer to make a CustomUser model at the start of a project. At first the attributes being stored are quite minimal but I end up accumulating some data into the user model at the end.
"Using a custom user model when starting a project" in django documentation also highlights this: https://docs.djangoproject.com/en/3.0/topics/auth/customizing/#using-a-custom-user-model-when-starting-a-project On Tuesday, May 5, 2020 at 6:46:14 PM UTC+5:30, Debjyoti Biswas wrote: > > Hi > > I am a new Django user, I am working on a platform and I chose Django to > develop it solely because of how "batteries included" it feels. > > I have to create users for my platform when they sign up, I was just > wondering if its best practice to use `User` from > `django.contrib.auth.models` for this. The user in my case will have > different levels of access and also there will be different types of users > like Vendors and Clients, logically I would use different user Models. > > Just wondering what's the best practice. > > Regards > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/af2476d5-0170-496e-9a69-e90f69c8ab38%40googlegroups.com.
