summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorCarlton Gibson <carlton.gibson@noumenal.es>2024-09-16 22:40:11 +0200
committerNatalia <124304+nessita@users.noreply.github.com>2024-09-16 17:41:36 -0300
commitd96b6611358b35f89a89d24150e30c260574efc0 (patch)
treeb6566e92e3a6c0c024b8cfd719c9e61eac081846 /docs
parentc12fe0a7243881aabe9ad6b04a447d0f7a496add (diff)
[5.1.x] Fixed #35767 -- Adjusted customizing User model docs.
Backport of c0128e3a81cfb07238324b185958a88631e94963 from main.
Diffstat (limited to 'docs')
-rw-r--r--docs/topics/auth/customizing.txt9
1 files changed, 4 insertions, 5 deletions
diff --git a/docs/topics/auth/customizing.txt b/docs/topics/auth/customizing.txt
index 52fa3515b8..3839c8608b 100644
--- a/docs/topics/auth/customizing.txt
+++ b/docs/topics/auth/customizing.txt
@@ -400,10 +400,9 @@ the Django model that you wish to use as your user model.
Using a custom user model when starting a project
-------------------------------------------------
-If you're starting a new project, it's highly recommended to set up a custom
-user model, even if the default :class:`~django.contrib.auth.models.User` model
-is sufficient for you. This model behaves identically to the default user
-model, but you'll be able to customize it in the future if the need arises::
+If you're starting a new project, you can set up a custom user model that
+behaves identically to the default user model by subclassing
+:class:`~django.contrib.auth.models.AbstractUser`::
from django.contrib.auth.models import AbstractUser
@@ -426,7 +425,7 @@ Changing to a custom user model mid-project
-------------------------------------------
Changing :setting:`AUTH_USER_MODEL` after you've created database tables is
-significantly more difficult since it affects foreign keys and many-to-many
+possible, but can be complex, since it affects foreign keys and many-to-many
relationships, for example.
This change can't be done automatically and requires manually fixing your