mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-03 18:38:50 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fixed #29683 -- Added view permission to docs.

Browse source
This commit is contained in:
Stephen James 2018-09-26 15:06:43 -04:00 • committed by Tim Graham
parent fb2964a410
commit e40e7026ca
4 changed files with 11 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

13
docs/topics/auth/customizing.txt
View file

@ -273,14 +273,13 @@ Custom permissions
To create custom permissions for a given model object, use the ``permissions``
:ref:`model Meta attribute <meta-options>`.
This example Task model creates three custom permissions, i.e., actions users
can or cannot do with Task instances, specific to your application::
This example ``Task`` model creates two custom permissions, i.e., actions users
can or cannot do with ``Task`` instances, specific to your application::
class Task(models.Model):
...
class Meta:
permissions = (
("view_task", "Can see available tasks"),
("change_task_status", "Can change the status of tasks"),
("close_task", "Can remove a task by setting its status as closed"),
)
@ -289,11 +288,11 @@ The only thing this does is create those extra permissions when you run
:djadmin:`manage.py migrate <migrate>` (the function that creates permissions
is connected to the :data:`~django.db.models.signals.post_migrate` signal).
Your code is in charge of checking the value of these permissions when a user
is trying to access the functionality provided by the application (viewing
tasks, changing the status of tasks, closing tasks.) Continuing the above
example, the following checks if a user may view tasks::
is trying to access the functionality provided by the application (changing the
status of tasks or closing tasks.) Continuing the above example, the following
checks if a user may close tasks::
user.has_perm('app.view_task')
user.has_perm('app.close_task')
.. _extending-user:

4
docs/topics/auth/default.txt
View file

@ -196,8 +196,8 @@ Default permissions
-------------------
When ``django.contrib.auth`` is listed in your :setting:`INSTALLED_APPS`
setting, it will ensure that three default permissions -- add, change and
delete -- are created for each Django model defined in one of your installed
setting, it will ensure that four default permissions -- add, change, delete,
and view -- are created for each Django model defined in one of your installed
applications.
These permissions will be created when you run :djadmin:`manage.py migrate