Skip to content

Commit 21df8ef

Browse files
[IMP] Settings: Access Rights Images
closes #12692 X-original-commit: 4d37ddb Signed-off-by: Samuel Lieber (sali) <[email protected]> Signed-off-by: Justin Mallette (juma) <[email protected]>
1 parent 7ae9eac commit 21df8ef

File tree

5 files changed

+6
-10
lines changed

5 files changed

+6
-10
lines changed

Diff for: content/applications/general/users/access_rights.rst

+6-10
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,6 @@ to the database, but they can be adjusted at any point in the user's profile.
3737
To make changes to a user's rights, click on the desired user to edit their profile.
3838

3939
.. image:: access_rights/navigate-to-users-menu.png
40-
:align: center
4140
:alt: Users menu in the Users & Companies section of the Settings app of Odoo.
4241

4342
On the user's profile page, in the :guilabel:`Access Rights` tab, scroll down to view the current
@@ -51,7 +50,6 @@ The :guilabel:`Administration` field in the :guilabel:`Access Rights` tab has th
5150
:guilabel:`Settings` or :guilabel:`Access Rights`.
5251

5352
.. image:: access_rights/user-permissions-dropdown-menu.png
54-
:align: center
5553
:alt: The Sales apps drop-down menu to set the user's level of permissions.
5654

5755
.. _access-rights/groups:
@@ -67,7 +65,6 @@ To access groups, first activate Odoo's :ref:`developer mode <developer-mode>`,
6765
:menuselection:`Settings app --> Users & Companies --> Groups`.
6866

6967
.. image:: access_rights/click-users-and-companies.png
70-
:align: center
7168
:alt: Groups menu in the Users & Companies section of the Settings app of Odoo.
7269

7370
To create a new group from the :guilabel:`Groups` page, click :guilabel:`Create`. Then, from the
@@ -83,11 +80,10 @@ this group was created to set access rights for sharing data with some users.
8380
Always test the settings being changed to ensure they are being applied to the correct users.
8481

8582
The group form contains multiple tabs for managing all elements of the group. In each tab, click
86-
:guilabel:`Add a line` to add a new row for users or rules, and click the :guilabel:`❌ (remove)`
87-
icon to remove a row.
83+
:guilabel:`Add a line` to add a new row for users or rules, and click the :icon:`fa-times`
84+
:guilabel:`(cancel)` icon to remove a row.
8885

8986
.. image:: access_rights/groups-form.png
90-
:align: center
9187
:alt: Tabs in the Groups form to modify the settings of the group.
9288

9389
- :guilabel:`Users` tab: lists the current users in the group. Users listed in black have
@@ -110,7 +106,7 @@ icon to remove a row.
110106
selected in the :guilabel:`Model` column.
111107

112108
To link a new access right to a group, click :guilabel:`Add a line`. Select the appropriate model
113-
from the :guilabel:`Model` dropdown, then enter a name for the access right in the
109+
from the :guilabel:`Model` drop-down, then enter a name for the access right in the
114110
:guilabel:`Name` column. For each model, enable the following options as appropriate:
115111

116112
- :guilabel:`Read`: Users can see the object's existing values.
@@ -120,14 +116,14 @@ icon to remove a row.
120116

121117
.. tip::
122118
While there are no conventions for naming access rights, it is advisable to choose a name that
123-
easily identifies its purpose.
119+
identifies its purpose.
124120

125121
For example, the access that purchase managers have to the :guilabel:`Contact` model could be
126122
named `res.partner.purchase.manager`. This consists of the technical name of the model,
127123
followed by a name identifying the group of users in question.
128124

129125
.. image:: access_rights/name-field.png
130-
:alt: Name of access rights to a model
126+
:alt: Name of access rights to a model.
131127

132128
To find the model's technical name from the current view, first enter a placeholder text
133129
in the :guilabel:`Name` field, then click the :guilabel:`Model` name, then the
@@ -161,7 +157,7 @@ Superuser mode
161157

162158
*Superuser mode* allows the user to bypass record rules and access rights. To activate *Superuser
163159
mode*, first, activate :ref:`developer mode <developer-mode>`. Then, navigate to the *debug* menu,
164-
represented by a :guilabel:`🪲 (bug)` icon, located in the top banner.
160+
represented by a :icon:`fa-bug` :guilabel:`(debug)` icon, located in the top banner.
165161

166162
Finally, towards the bottom of the menu, click :guilabel:`Become Superuser`.
167163

Loading
-2.01 KB
Loading
Loading
Loading

0 commit comments

Comments
 (0)