##// END OF EJS Templates
files: use ref names in the url, and make usage of default landing refs....
files: use ref names in the url, and make usage of default landing refs. - fixes #5601 - cleanup file edit/delete/add to use common breadcrumbs functions - make the urls with ref names persistent in case we have the landing ref selected - in most cases we only want to show refs instead of full commit-id, this is how other types of tools work anyway

File last commit:

r1:854a839a default
r4372:7db766f9 stable
Show More
sec-instance-basics.rst
31 lines | 1.2 KiB | text/x-rst | RstLexer
/ docs / admin / sec-instance-basics.rst

3 Basic User Security Steps

By implementing the following user configuration tasks, you will help to secure your |RCE| instances.

Define the Instance Wide Default User

The default user settings are applied across the whole instance. You should define the default user so that newly created users immediately have permission settings attached to their profile. For more information about defining the default user settings, see the :ref:`default-perms` section.

Configure Specific User Groups

By defining user groups, it allows you to put users into them and have the group permissions applied to their profile. For more information about defining the default user settings, see the :ref:`user-admin-set` section.

Define the Default User in Each Group

Apart from the system wide user permissions, each user group can apply its settings to the default user permissions within the scope of the group. To set the default user's permissions inside a user group, see the :ref:`permissions-info-repo-group-access` section.