> I understand that we can now have several admin site for the same app. (by proper configuration in the url_conf).
Yes with using of several AdminSite instances. So you can register models to needed site instance. That helps you to separate access to models from different admin backends. On Tue, Nov 18, 2008 at 13:50, Manakel <[EMAIL PROTECTED]> wrote: > > Hello All, > > I understand that we can now have several admin site for the same app. > (by proper configuration in the url_conf). > So it's allow to provide different layout of the admin interface to > different people of the project. > > However i don't understand if you can restrict the models of a app > that are available to an AdminSite. > > For example i want the models Users,Groups,MailBoxes to be available > via AdminSite 1 but not via AdminSite2. > And model "Requirement" to be shown differently in AdminSite1 than in > AdminSite2. > > Is it feasible? or do i hit the level to which Fully Homemade Forms > are better than customizing the Admin Module? > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
