I wrote about this a bit in a blog post here - http://www.satchmoproject.com/blog/2008/nov/28/using-django-permissions/
It's really easy to create any permissions using meta then access them in your views. While the permission is created in the models Meta section, you can certainly use it anywhere you like. My example above which creates a Is_member permission is used in multiple views so it is not tied to one specific model. Hope this helps. -Chris On Sun, Dec 7, 2008 at 12:10 AM, mh983 <[EMAIL PROTECTED]> wrote: > > What is the best way to create permissions for use in authorization if > those permissions aren't related to any specific model? I can't seem > to find anything to tell me how to do this. In fact, it looks like > even the database tables for permissions assume they are associated > with a model (auth_permission table has a content_type_id and the > content_type table refers to a model). > > For example. I'd like to restrict certain buttons on a form or certain > links to particular users. Also, I want to have my own page for a > superuser to see and enable/disable these permissions for any user, so > my solution needs to take that into account as well. > > Should I create my own Permission model with a ForeignKey to the built- > in User model? > > Any help on the best way to do this would be appreciated. I'm just > getting started converted my application to django and I'm stuck on > this. > > thanks, > > mike > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
