Changes between Version 35 and Version 36 of RowLevelPermissions

Timestamp:

Nov 23, 2006, 9:54:54 PM (17 years ago)

Author:

Adrian Holovaty

Comment:

Made some edits. Still working on it.

RowLevelPermissions

@@ +1 @@
+= Row-level permissions =
+
 == Introduction ==
 
-=== What are Row Level Permissions? ===
-
-An example of row level permissions would be: "User A has read-access to article 234" or "User D has read, write access to article 234".
+=== What are row-level permissions? ===
+
+Some examples of row-level permissions: "User A has read-access to article 234" or "User D has read, write access to article 234."
 
 === Why do we need this? ===
 
-An example of where this would be useful is a forum or message board. With the current permission system, a user is capable of editing all the posts or unable to edit any posts. After implementing a row level permission, it can be modified so a user is capable of editing only their own personal posts.
-
-== Using Row Level Permissions ==
-
-=== Basic Idea ===
-
-There are a few things you need to know about row level permissions before working with them:
-
- * Row level permissions use the permissions table to determine an object's possible permissions, you need to create permissions in the permissions table before using them in row level permissions.
- * Row level permissions can be negative, this is determined by an attribute called "negative". 
- * The order of checking permissions will work in the following order: User Row Level Permission -> Group Row Level Permission -> User Model Level Permission -> Group Model Level Permission. The checking will stop either at the first positive or negative, and if no permission is found will return a negative (or false).
-
-=== Enabling Row Level Permissions ===
-
-Enabling row level permissions is done by using the Meta class, you enable row level permissions by setting the "row_level_permissions" attribute to true. By default, row level permissions are assumed to be disabled.
-
-Example: To enable row level permissions for the mineral model, the model would look like:
+With the current permission system, a user of Django's admin interface is capable either of editing *all* objects of a certain type or editing *none* of the objects of a certain type. After implementing a row level permission, the user can be capable of editing only certain objects of that type -- e.g., just the objects he created himself.
+
+=== Status in Django ===
+
+Row-level permissions are being implemented in a branch -- the [http://code.djangoproject.com/browser/django/branches/per-object-permissions per-object-permissions branch]. This branch needs your help in testing. To get the code, use this Subversion command:
+
+{{{
+svn co http://code.djangoproject.com/svn/django/branches/per-object-permissions
+}}}
+
+== Using row-level permissions ==
+
+=== The basics ===
+
+There are a few things you need to know about row-level permissions before working with them:
+
+ * Row-level permissions use the permissions table to determine an object's possible permissions. You need to create permissions in the permissions table before using them in row-level permissions.
+ * Row-level permissions can be negative. This is determined by an attribute called "negative."
+ * Django checks permissions in the following order:
+   * User row-level permission
+   * Group row-level permission
+   * User model-level permission
+   * Group model-level permission
+   The checking stops either at the first positive or negative. If no permission is found, it will return a negative (or false).
+
+=== Enabling row-level permissions ===
+
+To enable row-level permissions for a model, add a {{{row_level_permissions = True}}} to the model's {{{class Meta}}}. By default, row-level permissions are disabled.
+
+For example:
+
 {{{
 #!python
@@ -32 +48 @@
     class Admin:
         pass
-    
+
     class Meta:
-        unique_together = (('name', 'hardness'),)
         row_level_permissions = True
-  
+
     def __str__(self):
         return self.name
 }}}
 
-You do not need the ''class Admin'' but it does create the default change, add and delete permissions for the object which are useful to have.
-
-=== Creating a Row Level Permission ===
-
-There are two helper methods to create row level permissions. These can be accessed by using the Row Level Permissions manager (e.g. RowLevelPermission.objects)
-
-The first is create_row_level_permission:
+The {{{class Admin}}} is not required, but its presence does create the default add/change/delete model-level permissions, which are useful to have.
+
+=== Creating a row-level permission ===
+
+Django has two helper methods for use in creating row-level permissions. They both live on the {{{RowLevelPermission}}} model manager (i.e., {{{RowLevelPermission.objects}}}).
+
+The first helper function is {{{create_row_level_permission}}}:
+
 {{{
 #!python
 def create_row_level_permission(self, object_instance, owner_instance, permission, negative=False):
-   ...
-}}}
-The permission parameter can either be the codename of the permission or a permission instance. The negative parameter is optional and will default to false. You must pass an instance of the object and owner to this method.
-
-The second is create_default_row_permissions:
+   # ...
+}}}
+
+The permission parameter can either be the codename of the permission or a permission instance. The negative parameter is optional and defaults to {{{False}}}. You must pass an instance of the object and owner to this method.
+
+The second helper function is {{{create_default_row_permissions}}}:
+
 {{{
 #!python
 def create_default_row_level_permissions(self, object_instance, owner_instance, change=True, delete=True, negChange=False, negDel=False):
-   ...
-}}}
-This will set up a row level permission with the default permissions set up for an object. The default permissions are: add, change and delete. 
-
-An example of its use, this creates a change row level permission on the quartz object:
-{{{
-#!python
-...
-RowLevelPermissions.objects.create_default_row_level_permissions(quartz, user, delete=False)
-...
-}}}
-
-=== Checking Permissions ===
-
-GenericAuthorization and row level permissions will eventually be merged. Therefore, I have shown two different methods of checking for permissions, one using the generic authorization and the currently implemented technique.
-
-The current method uses the has_perm method in the User model. Note: The object parameter is optional, this is to allow backwards compatibility, so if you do not want to check for row level permissions do not include the object parameter.
-
-Example:
-{{{
-#!python
-...
+   # ...
+}}}
+
+This will set up a row-level permission with the default permissions set up for an object. The default permissions are: add, change and delete.
+
+For example, this creates a change row-level permission on the {{{quartz}}} object:
+
+{{{
+#!python
+RowLevelPermission.objects.create_default_row_level_permissions(quartz, user, delete=False)
+}}}
+
+=== Checking permissions ===
+
+To check whether a user has permission to edit an object, use the {{{has_perm()}}} method on the {{{User}}} object:
+
+{{{
+#!python
 user.has_perm("mine.can_mine", object=mineral)
-...
-}}}
-
-This will return either True or False depending on if the user has the correct permission. It will return false if the user has a negative row level permission on the object. 
-
-This will also check group row level permissions. If the user is in two groups, the first having a positive row level permission and the second having a negative row level permission, it will take the positive row level permission over the negative.
-
-'''Second method using GenericAuthorization will be written after the merge. It will follow the documentation written on GenericAuthorization'''
-
-==== Has Row Level Permission ====
-
-The method contains_permission checks if the user has the given permission on a model (not an instance of a model but the model). This checks if there is exists the given row level permission on any of the instances of the model. It is used in the admin interface to determine if the change list should be shown to the user.
-
-E.g. If user A has change permission on article 234, and you did:
-{{{
-#!python
-...
-userA.contains_permission("mine.change_mineral", Mineral)
+}}}
+
+The {{{object}}} parameter is optional for backwards-compatibility. If you don't want to check row-level permissions, exclude the {{{object}}} parameter.
+
+{{{has_perm()}}} returns either {{{True}}} or {{{False}}}. It returns {{{False}}} if the user has a negative row-level permission on the object. It also checks group row-level permissions. If the user is in two groups, the first having a positive row-level permission and the second having a negative row-level permission, it will take the positive permission over the negative.
+
+Note that the GenericAuthorization branch (yet another of Django's many current branches) implements a different way of checking permissions. See the GenericAuthorization page for how row-level permissions fit in with that scheme.
+
+==== Has row-level permission ====
+
+The method {{{contains_permission()}}} checks whether the user has the given permission on a model -- not an *instance* of a model but the model itself. This checks if there is exists the given row level permission on any of the instances of the model. It is used in the admin interface to determine if the change list should be shown to the user.
+
+E.g. If {{{some_user}}} has change permission on article 234, and you did:
+{{{
+#!python
+...
+some_user.contains_permission("mine.change_mineral", Mineral)
 ...
 }}}