My own observation, from years on this mailing list, is that the dev team do not consider this a must-have for Django; their view (as far as I understand it!) is that the admin is designed for trusted users, so simply do not let them have access at all. Having said that, there is a pull request underway for a feature that seems similar to what you want:
https://github.com/django/django/pull/5297 (P.S. Also bear in mind that Django, like most FOSS projects, is not actually a democracy - so something 'the people want" does not necessarily get done; not understanding this trips many people up...) On Monday, 30 May 2016 20:13:18 UTC+2, Ander Ustarroz wrote: > > I am surprised this feature is not implemented yet, at the moment when we > create a new model three permissions are created automatically: > > - > - *add_permission* > - *change_permission* > - > *delete_permission * > > We really missing the *view_permission* here, when we want staff to be > able to see the content but not being able to modify it. Searching a bit, > you can find many different implementations to achieve this, but all of > them are extending django.contrib.*admin.**ModelAdmin*. Having so many > people rewriting these methods in my opinion is a clear sign that this > feature should be part of the core. > > Regards, > > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To post to this group, send email to django-users@googlegroups.com. Visit this group at https://groups.google.com/group/django-users. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/078b25c1-1ee1-4c67-9870-d41ee0e884db%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
