Browse files

Fixed #6927: Corrected documentation describing when and why the aut…

…h application creates default permissions

git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
ubernostrum committed Mar 30, 2008
1 parent 502f0c1 commit 38d30e96914c28d116a5a93a1d6a90e3a6a00135
Showing with 11 additions and 10 deletions.
  1. +11 −10 docs/authentication.txt
@@ -819,16 +819,17 @@ Django developers are currently discussing.
Default permissions
-Three basic permissions -- add, change and delete -- are automatically created
-for each Django model that has a ``class Admin`` set. Behind the scenes, these
-permissions are added to the ``auth_permission`` database table when you run
-`` syncdb``.
-Note that if your model doesn't have ``class Admin`` set when you run
-``syncdb``, the permissions won't be created. If you initialize your database
-and add ``class Admin`` to models after the fact, you'll need to run
-`` syncdb`` again. It will create any missing permissions for
-all of your installed apps.
+When ``django.contrib.auth`` is listed in your ``INSTALLED_APPS``
+setting, it will ensure that three default permissions -- add, change
+and delete -- are created for each Django model defined in one of your
+installed applications.
+These permissions will be created when you run `` syncdb``;
+the first time you run ``syncdb`` after adding ``django.contrib.auth``
+to ``INSTALLED_APPS``, the default permissions will be created for all
+previously-installed models, as well as for any new models being
+installed at that time. Afterward, it will create default permissions
+for new models each time you run `` syncdb``.
Custom permissions

0 comments on commit 38d30e9

Please sign in to comment.