##// END OF EJS Templates
permissions: handle more cases for invalidating permission caches...
permissions: handle more cases for invalidating permission caches - invalidate user permissions on chaning the global permissions - invalidate all users in case of creating new object with "copy permissions" flag - invalidate all users permissions in case of repo/repo group renames - invalidate all user permissions in forked repo with copy flag

File last commit:

r1:854a839a default
r3411:2e06ebce stable
Show More
default-user-perms.rst
31 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / admin / default-user-perms.rst
project: added all source files and assets
r1 .. _default-perms:
Default User Permissions
------------------------
There are two ways in which the default user settings work:
System-wide Level
^^^^^^^^^^^^^^^^^
On a system-wide level, you can set the default user permissions so that
all new users are given a certain set of permissions unless individually
tailored, or added to a user group. For more information about system-wide
default permissions, see the :ref:`permissions-info-anon-ref` and
:ref:`permissions-default-ref` sections.
User Group Level
^^^^^^^^^^^^^^^^
On a user group level, you can set the default user settings for the user
group, and all users within that group will get those default permissions
unless individually tailored. For more information about setting default
permissions for all the different entities, see the
:ref:`permissions-default-ref` section.
For more detailed information about managing the different permissions
settings, see the following sections:
* :ref:`permissions-info-anon-ref`
* :ref:`permissions-add-user`
* :ref:`permissions-default-ref`
* :ref:`permissions-info-add-group-ref`