On Tue, Nov 24, 2009 at 11:16 PM, rebus_ <r.dav...@gmail.com> wrote: > 2009/11/24 nek4life <nek4l...@gmail.com>: >> You should look into django-authority. I'm pretty sure that has per- >> object-permissions. >> >> http://packages.python.org/django-authority/index.html >> >> On Nov 24, 7:00 am, gamliel roi <roi.gaml...@gmail.com> wrote: >>> Hello all, >>> >>> I have the admin site up and running but I need to create a group of users, >>> such that each of the users will be able to edit objects that are only >>> relevant to them (e.g Project objects that the user is also the >>> ProjectManager). >>> >>> I know that in the past Django had a Per-object permissions branch, which is >>> now abandoned. >>> >>> Should I peruse this direction and try to incorporate this branch to my >>> current code? is it documented and running properly? >>> >>> Any other ideas/suggestions/resources regarding this problem? >>> >> > Row level permisions should be implemented in Django version 1.2 [1] > if you have the time to wait... > > [1] http://code.djangoproject.com/wiki/Version1.2Features
To be clear - that ticket *doesnt'* implement row-level permissions; it modifies the calls for permission checks to allow you to build a row-level permissions checker external to Django. Yours, Russ Magee %-) -- 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.
