Hi Manakel, On Nov 6, 11:53 am, Manakel <[EMAIL PROTECTED]> wrote: > This web application had a Authorization model at the Field level. > [....] > TASK has a progress status field and a due date field > realisator user can only change the status field > owner can change both the status field and the > initalize the due date field project manager can initialize the due > date field but also change it. > Is there any best practice to manage this kind of very fine grained > authorisations in Django?
You can use many-to-one relation to split Task for more then one model. http://www.djangoproject.com/documentation/models/many_to_one/ Task(models.Model): Description DueDate(models.Model): task = models.ForeignKey(Task) due_date Status(models.Model): task = models.ForeignKey(Task) status And now, you can assign permission individually for every model. Regards, Marcin -- http://www.zenzire.com | Software Development Company --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
