Skip to content

Commit 23edfdc

Browse files
authored
Update security.rst
1 parent e9a7047 commit 23edfdc

1 file changed

Lines changed: 14 additions & 10 deletions

File tree

en/functions/backend/FOM/security.rst

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -11,14 +11,15 @@ Security as provided by the FOMUserBundle is anchored on these base concepts:
1111

1212

1313
Rights management
14-
================================================================================
14+
=================
15+
1516
Mapbender provides different rights. They refer to the :doc:`Access Control Lists (ACL) <acl>`.
1617

1718
* view - Whether someone is allowed to view the object.
1819
* edit - Whether someone is allowed to make changes to the object.
1920
* delete - Whether someone is allowed to delete the object.
2021
* operator - Whether someone is allowed to perform all of the above actions.
21-
* master - Whether someone is allowed to perform all of the above actions, and in addition is allowed to grant any of the above permissions to others.
22+
* master - Whether someone is allowed to perform all of the above actions and in addition is allowed to grant any of the above mentioned permissions to others.
2223
* owner - Whether someone owns the object. An owner can perform any of the above actions and grant master and owner permissions.
2324

2425
Assign roles to a user by ``Users --> Edit your User --> Security``.
@@ -28,41 +29,44 @@ Assign roles to a user by ``Users --> Edit your User --> Security``.
2829

2930

3031
Assign an Application to a User/Group
31-
================================================================================
32+
=====================================
33+
3234
#. Edit your application by ``Application --> Edit-Button``.
3335

3436
#. Choose ``Security``.
3537

36-
#. Publish or hide your application for everyone by clicking ``Security --> public access`` or in the application overview by clicking the ``Publish button``.
38+
#. Publish or hide your application for everyone by clicking ``Security --> public access`` or in the application overview by clicking the ``Publish`` button.
3739

38-
#. Alternatively and for an individual configuration, click the ``Add users and groups`` button and configure your selection. Then, set permissions like view, edit, delete, operator, master, owner via the rights table.
40+
#. Alternatively and for an individual configuration, click the ``Add users and groups`` button and configure your selection. Then, set permissions like view, edit, delete, operator, master or owner via the rights table.
3941

4042
#. Logout from Mapbender by ``Logout`` and log in again with a configured account to test the configuration.
4143

4244
#. Another method would be to choose ``Security --> Global Access Control Lists --> Applications`` to quickly set permissions for several users/groups to all applications.
4345

4446

4547
Assign single elements to a User/Group
46-
================================================================================
48+
======================================
49+
4750
Per default, all elements are available to all users/groups that have permission to an application. It is possible to hide single elements from individual users/groups like this:
4851

4952
#. Edit your application by clicking ``Application --> Edit``.
5053

5154
#. Choose ``Layouts``.
5255

53-
#. Every element has a ``Acl element`` button (key). Choose the ``Acl element`` button from the element that should be only availale for selected users/groups.
56+
#. Every element has a ``ACL element`` button (key). Choose the ``ACL element`` button from the element that should be only availale for selected users/groups.
5457

55-
#. Now, add the users/groups via the ``Add users and groups`` button. Then, set permissions like view, edit, delete, operator, master, owner via the rights table.
58+
#. Now, add the users/groups via the ``Add users and groups`` button. Then, set permissions like view, edit, delete, operator, master or owner via the rights table.
5659

5760
#. Test your configuration. For example, open the application with a user account that has (no) rights to a previously configured element.
5861

5962

6063
Assign a user to another User/Group
61-
================================================================================
64+
===================================
65+
6266
#. Edit a user by clicking ``Security --> Users``.
6367

6468
#. In the user administration, choose ``Security``.
6569

6670
#. Give users/groups individual rights on the selected user: Add users/groups via the ``Add users and groups`` button. Thereafter, set permissions within the rights table.
6771

68-
#. You have now assigned a user/group controlling options over another user account. Test your configuration with the entitled user accounts.
72+
#. You have now assigned a user/group controlling options over another user account. Test your configuration with the entitled user accounts.

0 commit comments

Comments
 (0)