##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
shadow-repos: use safer way to destroy shadow repositories....
shadow-repos: use safer way to destroy shadow repositories. we had reported errors on removal of shadow repos. Not reproduced, however suspecting are filesystem sync/symlink race-conditions on shared storage. End result were existing shadow-repo directories that tricked rhodecode into thinking shadow repos is existing, but infact it was a dummy structure semi-removed. Using shutil.move we ENSURE rhodecode doesn't read those back even if removal fails.
marcink - - Load All Authors

File last commit:

r1:854a839a default
r2777:f1cc2e3d default
Show More
default-user-perms.rst
31 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / admin / default-user-perms.rst
History | Source | Raw |Copy content |Copy permalink
marcink
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`