##// END OF EJS Templates
scm-app: allow to set documented pyro4 as scm_app_implementation....
scm-app: allow to set documented pyro4 as scm_app_implementation. The documented ini setting allows to set pyro4 as scm_app, while the backend code crashes on import of pyro4 module. This change allows to configure the app based on the .ini docs. if we pass pyro4 as backedn, we simply skip import and use the default pyro4 scm_app

File last commit:

r1:854a839a default
r632:064401fe default
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`