From 38d30e96914c28d116a5a93a1d6a90e3a6a00135 Mon Sep 17 00:00:00 2001 From: James Bennett Date: Sun, 30 Mar 2008 13:35:12 +0000 Subject: [PATCH] Fixed #6927: Corrected documentation describing when and why the auth application creates default permissions git-svn-id: http://code.djangoproject.com/svn/django/trunk@7388 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/authentication.txt | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/docs/authentication.txt b/docs/authentication.txt index 9167458db2..79eaf673e7 100644 --- a/docs/authentication.txt +++ b/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 -``manage.py syncdb``. +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. -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 -``manage.py syncdb`` again. It will create any missing permissions for -all of your installed apps. +These permissions will be created when you run ``manage.py 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 ``manage.py syncdb``. Custom permissions ------------------