diff --git a/docs/topics/auth.txt b/docs/topics/auth.txt
index c3a2636..fd533e9 100644
|
a
|
b
|
The Django admin site uses permissions as follows:
|
| 1493 | 1493 | * Access to delete an object is limited to users with the "delete" |
| 1494 | 1494 | permission for that type of object. |
| 1495 | 1495 | |
| 1496 | | Permissions are set globally per type of object, not per specific object |
| 1497 | | instance. For example, it's possible to say "Mary may change news stories," but |
| 1498 | | it's not currently possible to say "Mary may change news stories, but only the |
| 1499 | | ones she created herself" or "Mary may only change news stories that have a |
| 1500 | | certain status, publication date or ID." The latter functionality is something |
| 1501 | | Django developers are currently discussing. |
| | 1496 | Permissions can be set not only per type of object, but also per specific |
| | 1497 | object instance. By using the has_add_permission, has_change_permission and |
| | 1498 | has_delete_permission methods, provided by the ``ModelAdmin`` class, it is |
| | 1499 | possible to customize permissions for different object instances of the same |
| | 1500 | type. |
| 1502 | 1501 | |
| 1503 | 1502 | Default permissions |
| 1504 | 1503 | ------------------- |