There's some good stuff in here. My requirements are a little different than straight-up row level security.
I have a working prototype that I'm going to post on github later today. It was a lot easier than I thought it would be. It uses all the standard django permissions (create/change/delete object) but then adds the concept of a namespace. This could be considered a group, but I hesitate to use that term since it's already part of the django vocabulary and means something else. So lets say I create a namespace like so, and assign the user "tim" to it: http://i.imgur.com/uVaPGl.png Then I create a course and put it in that namespace: http://i.imgur.com/BIUBKl.png Only the user "tim" will have access to change that course, or create new courses in that namespace. The "wanda" user should never be aware of the fact that this course exists, since that user does not have access to the Global namespace.
-- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-us...@googlegroups.com. To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
