What you're describing is more of a row-level permissions system. The permissions system that ships with contrib.auth is table-level, not row-level. There has been some talk on this list about ways to go about it, but I don't think there's an out-of-the-box solution for it yet.
Off of the top of my head (and I'm hoping others will chime in with improvements), you can use a custom manager[1] for the Layer model which requires the request.user to be passed in. That way, you will be able to control access in the manager itself and hide that logic from your views. This is assuming that you have a foreign key to the user who created each Layer and, given request.user, will be able to determine what permissions they should have. Shawn [1] http://docs.djangoproject.com/en/1.1/topics/db/managers/#id2 -- 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.
