Ticket #13211: 13211.diff

docs/topics/auth.txt

@@ -1295 +1295 @@
 
 .. currentmodule:: django.contrib.auth
 
+
+Programmatically creating permissions
+-------------------------------------
+
+While custom permissions can be defined within a model's ``Meta`` class, you
+can also create permissions directly. For example, you can create the ``can_publish``
+permission for a ``BlogPost`` model in ``myapp``::
+
+    from django.contrib.auth.models import Group, Permission
+    from django.contrib.contenttypes.models import ContentType
+
+    content_type = ContentType.objects.get(app_label='myapp', model='BlogPost')
+    perm = Permission.objects.create(codename='can_publish', name='Can Publish Posts',
+         content_type=content_type)
+
+The permission can be assigned to a :class:`~django.contrib.auth.models.User` via
+``user_permissions`` or a :class:`~django.contrib.auth.models.Group` via
+``permissions``.
+
+
 Authentication data in templates
 ================================
 
@@ -1387 +1407 @@
 access to a members-only portion of your site, or send them members-only e-mail
 messages.
 
+.. class:: models.Group
+
+API reference
+-------------
+
+Fields
+~~~~~~
+
+.. class:: models.Group
+
+    :class:`~django.contrib.auth.models.Group` objects have the
+    following fields:
+
+    .. attribute:: models.Group.name
+
+        Required. 80 characters or fewer. Any characters are permitted.
+
+    .. attribute:: models.Group.permissions
+
+        Many-to-many field to :class:`~django.contrib.auth.models.Permissions`::
+
+            group.permissions = [permission_list]
+            group.permissions.add(permission, permission, ...)
+            group.permissions.remove(permission, permission, ...)
+            group.permissions.clear()
+
 Messages
 ========