##// END OF EJS Templates
rhodecode-enterprise-ce
RSS
svn: fixed case of wrong extracted repository name for SSH backend. In cases...
svn: fixed case of wrong extracted repository name for SSH backend. In cases where we commited to a nested subdirs SVN reported the access path with the subdir paths in it. We couldn't then match that extended name into proper rhodecode repository for ACL checks. - Current implementation gives an slight overhead as we have to lookup all repositories - fixes #5606
marcink - - Load All Authors

File last commit:

r3658:b7b32afd default
r4281:5da17e74 default
Show More
default-user-perms.rst
31 lines | 1.1 KiB | text/x-rst | RstLexer
/ docs / admin / user_admin / default-user-perms.rst
History | Annotation | Raw |Copy content |Copy permalink

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`