8
.. i18n: Three concepts are differentiated into Tiny ERP;
10
Three concepts are differentiated into Tiny ERP;
12
.. i18n: 1. The users: person identified by his login/password
13
.. i18n: 2. The groups: define the access rights of the resources
14
.. i18n: 3. The roles: determine the roles/duties of the users
16
1. The users: person identified by his login/password
17
2. The groups: define the access rights of the resources
18
3. The roles: determine the roles/duties of the users
20
.. i18n: .. figure:: images/module_base_user.png
22
.. i18n: :align: center
24
.. figure:: images/module_base_user.png
28
.. i18n: **The users**
32
.. i18n: They represent physical persons. These are identified with a login and a password. A user may belong to several groups and may have several roles.
34
They represent physical persons. These are identified with a login and a password. A user may belong to several groups and may have several roles.
36
.. i18n: A user must have an action set up. This action is executed when the user connects to the program with his login and password. An example of action would be to open the menu at 'Operations'.
38
A user must have an action set up. This action is executed when the user connects to the program with his login and password. An example of action would be to open the menu at 'Operations'.
40
.. i18n: The preferences of the user are available with the preference icon. You can, for example, through these preferences, determine the working language of this user. English is set by default.
42
The preferences of the user are available with the preference icon. You can, for example, through these preferences, determine the working language of this user. English is set by default.
44
.. i18n: A user can modify his own preferences while he is working with Tiny ERP. To do that, he clicks on this menu: User > Preferences. The Open ERP administrator can also modify some preferences of each and every user.
46
A user can modify his own preferences while he is working with Tiny ERP. To do that, he clicks on this menu: User > Preferences. The Open ERP administrator can also modify some preferences of each and every user.
48
.. i18n: **The groups**
52
.. i18n: The groups determine the access rights to the different resources. There are three types of right:
54
The groups determine the access rights to the different resources. There are three types of right:
56
.. i18n: * The writing access: recording & creation,
57
.. i18n: * The reading access: reading of a file,
58
.. i18n: * The execution access: the buttons of workflows or wizards.
60
* The writing access: recording & creation,
61
* The reading access: reading of a file,
62
* The execution access: the buttons of workflows or wizards.
64
.. i18n: A user can belong to several groups. If he belongs to several groups, we always use the group with the highest rights for a selected resource.
66
A user can belong to several groups. If he belongs to several groups, we always use the group with the highest rights for a selected resource.
68
.. i18n: **The roles**
72
.. i18n: The roles define a hierarchical structure in tree. They represent the different jobs/roles inside the company. The biggest role has automatically the rights of all the inferior roles.
74
The roles define a hierarchical structure in tree. They represent the different jobs/roles inside the company. The biggest role has automatically the rights of all the inferior roles.
84
.. i18n: + Technical manager
88
.. i18n: - Chief of projects
98
.. i18n: + Commercial manager
108
.. i18n: If we want to validate the test of a program (=role Testers), it may be done by a user having one of the following roles: Testers, Chief of the project, Technical manager, CEO.
110
If we want to validate the test of a program (=role Testers), it may be done by a user having one of the following roles: Testers, Chief of the project, Technical manager, CEO.
112
.. i18n: The roles are used for the transition of Workflow actions into confirmation, choice or validation actions. Their implications will be detailed in the Workflow section.
114
The roles are used for the transition of Workflow actions into confirmation, choice or validation actions. Their implications will be detailed in the Workflow section.
122
.. i18n: It's easy (but risky) to grant grained access to menu based on the user's groups.
124
It's easy (but risky) to grant grained access to menu based on the user's groups.
126
.. i18n: First of all, you should know that if a menu is not granted to any group then it is accessible to everybody ! If you want to grant access to some groups just go to **Menu > Administration > Security > Define access to Menu-items** and select the groups that can use this menu item.
128
First of all, you should know that if a menu is not granted to any group then it is accessible to everybody ! If you want to grant access to some groups just go to **Menu > Administration > Security > Define access to Menu-items** and select the groups that can use this menu item.
130
.. i18n: .. figure:: images/grant_access.png
132
.. i18n: :align: center
134
.. figure:: images/grant_access.png
138
.. i18n: Beware ! If the Administrator does not belong to one of the group, he will not be able to reach this menu again.
140
Beware ! If the Administrator does not belong to one of the group, he will not be able to reach this menu again.