Skip to content

Commit 208c2a2

Browse files
[IMP] Access Rights: Technical Access Rights
Co-authored-by: Felicia Kuan <[email protected]>
1 parent 4ab94a4 commit 208c2a2

File tree

1 file changed

+49
-7
lines changed

1 file changed

+49
-7
lines changed

content/applications/general/users/access_rights.rst

+49-7
Original file line numberDiff line numberDiff line change
@@ -28,8 +28,8 @@ should not have access to.
2828
Once complete, click :guilabel:`Save` to save the changes, and implement the user as an
2929
administrator.
3030

31-
Users
32-
=====
31+
Manage user permissions
32+
=======================
3333

3434
The access rights for :ref:`individual users <users/add-individual>` are set when the user is added
3535
to the database, but they can be adjusted at any point in the user's profile.
@@ -52,6 +52,48 @@ The :guilabel:`Administration` field in the :guilabel:`Access Rights` tab has th
5252
.. image:: access_rights/user-permissions-dropdown-menu.png
5353
:alt: The Sales apps drop-down menu to set the user's level of permissions.
5454

55+
Manage specific permissions
56+
---------------------------
57+
58+
While access rights are typically managed in a bundle, they can also be set for explicit
59+
permissions. For example, giving a user the :guilabel:`Administrator` permission for **Timesheets**
60+
gives them full access to that app. That user, however, can be made to have full access to the app,
61+
but their ability to manage their own timesheets restricted (e.g., if the payroll administrator is
62+
salaried and does not need to manage their own timesheets).
63+
64+
Manage specific permissions requires :ref:`developer mode <developer-mode>`. After that, navigate to
65+
:menuselection:`Settings app`, and then click :guilabel:`Manage users`, select a user, and go to the
66+
:guilabel:`Technical Access Rights` tab. From here, groups can be edited (which is covered in the
67+
next section) and specific access rights can be managed.
68+
69+
In the :guilabel:`Groups` section, these specific access rights are organized by groups and are
70+
split into sections. If no changes are made to these groups, then their permissions will mirror the
71+
selections made in the :guilabel:`Access Rights` tab.
72+
73+
- :guilabel:`Selected groups`: access rights set by choices made in the :guilabel:`Access Rights`
74+
tab
75+
- :guilabel:`Groups added automatically`: access rights given as part of the access rights provided
76+
by the :guilabel:`Selected groups`
77+
78+
To add a permission to this user profile, click :guilabel:`Add a line` in the :guilabel:`Selected
79+
groups` table, and then add permissions to this user profile. To remove a permission, click the
80+
:icon:`fa-times` :guilabel:`(cancel)` at the end of that permission's row.
81+
82+
Clicking on the permission itself will open a *group management form*. Learn more about
83+
:ref:`managing groups <access-rights/groups>`.
84+
85+
Any permission in the :guilabel:`Groups added automatically` section are implied or required by the
86+
permission shown in the :guilabel:`Selected groups` section. These cannot be removed, but more users
87+
can be given these permissions by clicking on the permission itself, and then adding the user to
88+
that permission's group.
89+
90+
.. note::
91+
Any permission in green is already provided by another permission (for example, setting the
92+
**Website** permission to :guilabel:`Editor and Designer` will also give that user the
93+
:guilabel:`Restricted Editor` permission). Any permissions in red are conflicting and cannot be
94+
active at the same time. Any permissions in *italics* is implied by a :guilabel:`Selected group`
95+
(these are usually found in the :guilabel:`Groups added automatically`).
96+
5597
.. _access-rights/groups:
5698

5799
Create and modify groups
@@ -102,8 +144,8 @@ The group form contains multiple tabs for managing all elements of the group. In
102144
- :guilabel:`Views` tab: lists which views in Odoo the group has access to. Click :guilabel:`Add a
103145
line` to add a view to the group.
104146
- :guilabel:`Access Rights` tab: lists the first level of rights (models) that this group has. The
105-
:guilabel:`Name` column represents the name for the current group's access to the model
106-
selected in the :guilabel:`Model` column.
147+
:guilabel:`Name` column represents the name for the current group's access to the model selected
148+
in the :guilabel:`Model` column.
107149

108150
To link a new access right to a group, click :guilabel:`Add a line`. Select the appropriate model
109151
from the :guilabel:`Model` drop-down, then enter a name for the access right in the
@@ -125,9 +167,9 @@ The group form contains multiple tabs for managing all elements of the group. In
125167
.. image:: access_rights/name-field.png
126168
:alt: Name of access rights to a model.
127169

128-
To find the model's technical name from the current view, first enter a placeholder text
129-
in the :guilabel:`Name` field, then click the :guilabel:`Model` name, then the
130-
:icon:`fa-arrow-right` :guilabel:`(Internal link)` icon.
170+
To find the model's technical name from the current view, first enter a placeholder text in the
171+
:guilabel:`Name` field, then click the :guilabel:`Model` name, then the :icon:`fa-arrow-right`
172+
:guilabel:`(Internal link)` icon.
131173

132174
- :guilabel:`Record Rules`: lists the second layer of editing and visibility rights.
133175
:guilabel:`Record Rules` overwrite, or refine, the group's access rights. Click :guilabel:`Add a

0 commit comments

Comments
 (0)