@@ -51,18 +51,18 @@ Grant access to the user_upload folder (file mounts)
5151
5252The :ref: `automatically created user groups <backend-users-groups-quick >` from
5353the previous step have access to the :guilabel: `Filelist ` module, however, as
54- file mount is created automatically they will only see an error message:
54+ file mount is created automatically, they will only see an error message:
5555
5656.. figure :: /Images/ManualScreenshots/BackendUser/MissingFolderPermissions.png
5757 :alt: Error message: Missing folder permissions. You have no access to the folder "1:/user_upload/".
5858
5959 Error message when a user with the auto-generated groups opens the Filelist module
6060
61- Unless your users or their groups have at least one file mount they will, not be
61+ Unless your users or their groups have at least one file mount they will not be
6262able to upload files including images.
6363
64- To create a file mount go to the backend module :guilabel: `File > Filelist `
65- then choose folder in for which you want to create a file mount.
64+ To create a file mount, go to the backend module :guilabel: `File > Filelist `
65+ then choose the folder in which you want to create a file mount.
6666
6767Right click on the folder in the directory tree and choose "New Filemount"
6868from the context menu:
@@ -75,8 +75,8 @@ from the context menu:
7575Then go to the module :guilabel: `System > Backend Users `, choose "Backend user
7676groups" from the dropdown in the module header and edit the group of your users.
7777
78- In tab "Mounts and Workspaces", select field "File Mounts" choose the newly
79- created file mount on the right to add it to the left side. After saving
78+ In tab "Mounts and Workspaces", select field "File Mounts", choose the newly
79+ created file mount on the right to add it to the left side. After saving,
8080backend users belonging to that group should be able to upload files.
8181
8282.. _backend-users-groups-manual :
@@ -89,7 +89,7 @@ in the Backend User module, refer to
8989`Setting up User Permissions <https://docs.typo3.org/permalink/t3coreapi:setting-up-user-permissions >`_.
9090
9191.. note ::
92- Incomplete backend permissions can lead to strange behaviour and even
92+ Incomplete backend permissions can lead to strange behaviour and
9393 exceptions in the backend. Simulate a backend user and test their permissions
9494 thoroughly.
9595
@@ -99,16 +99,16 @@ Backend user groups and page permissions
9999========================================
100100
101101Similar to a UNIX file system where each file belongs to exactly one user and
102- group each page in the page tree also belongs to one user (usually the one who
102+ group, each page in the page tree also belongs to one user (usually the one who
103103created it) and one group (the first group of that user).
104104
105- This can lead to problems because administrators often belong to no user group
106- and then the created pages will also belong to no group.
105+ This can lead to problems because administrators often do not belong to a user group
106+ and then the created pages will also not belong to a group.
107107
108108This leads to the situation that even though your editor has the right to see
109109the page tree "Backend user group > Mounts and Workspaces > DB Mounts" and they
110- have the other necessary permissions they still cannot see any pages because the
111- root page was create by an administrator and belongs to no group.
110+ have the other necessary permissions, they still cannot see any pages because the
111+ root page was created by an administrator and does not belong to a group.
112112
113113You can fix such page permissions recursively in the module :guilabel: `System >
114114Permissions `.
@@ -139,14 +139,14 @@ Technical details
139139=================
140140
141141Backend user groups and their permissions are stored in the database table
142- :sql: `be_groups `. At the time of writing there is no official solutions for
143- deployable backend user rights. You can however use the export / import module
142+ :sql: `be_groups `. At the time of writing there are no official solutions for
143+ deployable backend user rights. You can, however, use the export / import module
144144to export and import backend user groups.
145145
146146Backend user groups are database records that are stored on the virtual root
147- page (uid=0). They can therefore also be viewed an edited in the list module.
147+ page (uid=0). They can therefore also be viewed and edited in the list module.
148148
149149Backend user groups can inherit from one or several other user groups. In such
150150a setting it is possible to grant additional permissions of the parent user
151- group. It is however not possible to reduce the permissions of the parent user
151+ group. It is, however, not possible to reduce the permissions of the parent user
152152group.
0 commit comments