View Odoo Product Analysis Series - Catalog
1 Notes for administrators
Care must be taken when documenting important configuration details, and there must be a consistent plan in place to keep the system up and running for an acceptable period of time.
1.1 Develop an implementation strategy
If you want to use odoo to implement a business, it is very important to develop an implementation strategy. Here are a few factors to consider:
2 Manage users
As with any ERP system, it is important to fully understand how users and user permissions are managed. When odoo is first installed, an administrative user is automatically created, he is a super administrative user, and there is only one super administrator in the whole system. In some systems, any account can be designated as a super administrator, but in odoo, all permissions cannot be given to another user.
In particular, when using an administrator account, all access rights are ignored. Just like root account under Linux or Ubuntu system. Users are required to protect administrative accounts with strong passwords and keep them private.
2.1 Select a user as administrator
View the user list, click the user option under the user menu under the main menu of settings:
create a new user, the form corresponds to the res.user data table
Item : you can choose to set the user as an administrator or a common user.
Employee: You can choose to set the user as an employee (if an employee is managed in the system, the user can manage their own HR information, such as vacation requests, payroll, etc.) or a device administrator (the user can scrape glass devices).
Work meal, fleet: Users can be set as ordinary users or administrator users under this function.
System Administration: Optional access rights and settings.
After opening the developer mode, the following options will appear:
in the profile, you can make some localized settings, and you can specify different time zones and languages; in the message and social options, you can receive the user's E-mail messages. Settings; Alias Allows administrators to set up an E-mail alias; Signature Specifies a signature footer for emails sent by this user. :
Note that if you are an administrator making these changes for another user, changing these settings will require the user to log out of the system, thereby updating their session with the changes.
Home Action: If specified, this action will be executed along with the standard menu after the user account is logged in. That is to say, the first interface of login will display the specified menu page, such as the following actions, you can also create your own:
After saving, you can set the user password, click Change Password: After
entering the password, click Change Password:
Now you can log out of the current account and log in This user:
Log in to this account and only see the menus that you have permissions to:,
2.2 Group
In odoo, users are assigned permissions by assigning them to groups. Once a user is assigned to a group, the user has all permissions and options associated with that group. Typically, a user can belong to multiple groups. Turn on the "developer mode" to perform group related settings:
you can see that there are many groups in odoo. It takes a good understanding of how groups work to understand that when users are placed in a particular group, it is easy to determine what options and menus are available to users.
For example, for sales/admin groups, the form corresponds to the res.group data table:
as you can see from the application field, a group is always associated with an application.
Name: The name of the group, when displayed in the list, the odoo system automatically adds a slash (/) between the application and the name.
On the first option page, you can select a user and add a user to the group, indicating that the user has all the permissions of the current group.
(1) Group inheritance
In any ERP system, the management of authority is the key point. In Odoo, it is easier to implement permission management. It uses the inheritance mechanism. A group can inherit multiple groups, and a self-group can have all the permissions of the parent group. For example, the sales/admin group inherits the following groups:
this means that any user added to this group has the permissions of the group (sales/admin) and also has the website/Restricted Editor And Sales/Users: All permissions of the two groups of all documents, if these two groups also have their own inherited groups, the corresponding permissions can also be inherited...
(2) Menu
Groups provide a direct way to manage which menus a user can access: for example, users in the Sales/Admin group can access the following menus (but the parent group of the group cannot access these menus unless they themselves specify these menus):
For example, if you need Sales/Users: All users in the document group to be able to access the Sales/Reports/Activity menu, you can remove this menu from the Sales/Users group and add it to Sales/Users : In all document groups, but then all users in groups that inherit Sales/Users: All document groups can access this menu.
(3) View
Views are similar to menus. Specify which views users can view when accessing data.
(4) Access rights
Access rights define exactly which models the current group can access. In Odoo, a model represents a business entity object and its associated operations. Read access, write access, create access, and delete access can be specified for each object .
The access rights of the current sales/admin group are defined as follows:
For example, users of this group can read, write and create partners, but cannot delete:
(5) Rules
Sometimes in a system, you want users to access a specific model, not all records in that model. For example, you might want users to be able to access phones within the system. But for some groups, you only want users to have access to their own phone records, not everyone's phone in the system. You can define rules when you need to control user access based on the content of records in the model.
For example: in the Sales/Users: Own Documents group only, since this is a very restricted group, there are a lot of rules that restrict users in this group to only see records associated with them:
Typically, the Admin Group There are few or no rules because they have no restrictions on the records that can be accessed. Groups like Own Documents Only will have some rules because users can't see records they don't own. Check out the Personal Order rules to see how to build a rule that restricts user access to records (ir.rule data table):
The rules are described in detail at the bottom of the form. If the rule list does not specify a group, it means that the rule will apply to everyone/all groups. As you can see on the right side of the form, you can specify access rights for rules, so you can create a rule specifying that a user can access (read) certain records, but not create, write, or delete records.
The most important part is the rule definition (Domain filtering) . This is the filter applied to each record to determine if the record is available. In this rule, the system will check whether the user_id of the viewed record is equal to the user_id of the current system login. Specifically, the value here is true if you are viewing your own data records or records that are not assigned to any user.
When making your own rules, you can copy rules from similar rules and be able to determine grammatical correctness. In addition, changing the existing rules in the real-time system will cause some functions in the system to fail once the syntax is wrong.