Fixed #25166 -- Clarified how auth permissions are created.

            )

The only thing this does is create those extra permissions when you run

:djadmin:`manage.py migrate <migrate>`. 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::

: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::

    user.has_perm('app.view_task')

will be created for all previously-installed models, as well as for any new

models being installed at that time. Afterward, it will create default

permissions for new models each time you run :djadmin:`manage.py migrate

<migrate>`.

<migrate>` (the function that creates permissions is connected to the

:data:`~django.db.models.signals.post_migrate` signal).

Assuming you have an application with an

:attr:`~django.db.models.Options.app_label` ``foo`` and a model named ``Bar``,