Fixed #17131 - Added per object permission notes to docs.
Thanks dchandek for the suggestion and mateusgondim for the patch.
This commit is contained in:
parent
4129201c3e
commit
8d3e501502
|
@ -1476,12 +1476,13 @@ The Django admin site uses permissions as follows:
|
||||||
* Access to delete an object is limited to users with the "delete"
|
* Access to delete an object is limited to users with the "delete"
|
||||||
permission for that type of object.
|
permission for that type of object.
|
||||||
|
|
||||||
Permissions are set globally per type of object, not per specific object
|
Permissions can be set not only per type of object, but also per specific
|
||||||
instance. For example, it's possible to say "Mary may change news stories," but
|
object instance. By using the
|
||||||
it's not currently possible to say "Mary may change news stories, but only the
|
:meth:`~django.contrib.admin.ModelAdmin.has_add_permission`,
|
||||||
ones she created herself" or "Mary may only change news stories that have a
|
:meth:`~django.contrib.admin.ModelAdmin.has_change_permission` and
|
||||||
certain status, publication date or ID." The latter functionality is something
|
:meth:`~django.contrib.admin.ModelAdmin.has_delete_permission` methods provided
|
||||||
Django developers are currently discussing.
|
by the :class:`~django.contrib.admin.ModelAdmin` class, it is possible to
|
||||||
|
customize permissions for different object instances of the same type.
|
||||||
|
|
||||||
Default permissions
|
Default permissions
|
||||||
-------------------
|
-------------------
|
||||||
|
|
Loading…
Reference in New Issue