The confusion between permissions and rules: a real case
Imagine that in your company, a salesperson logs into Odoo and sees all sales orders, including their colleagues' commissions. At the same time, someone deleted an important order and nobody knows how it happened. Both situations share the same root: who can see and do what in Odoo? This is not solved out of the box; you configure it yourself. And it is configured with two mechanisms that everyone confuses: access rights and record rules. In this article you will master them from scratch, step by step and with real company examples. By the end, you will be able to decide with precision who sees what and who can do what in any Odoo.
Model, record and field: the three pillars of security
Before touching the security locks, you need to know what we are protecting. In Odoo, absolutely everything boils down to three words: model, record and field.
Model is a type of thing Odoo can handle. For example, contacts, sales orders, invoices, products. Each model has an internal name, such as product.product or account.move. When you click a menu, it usually takes you to a model.
Practical example: In a furniture company, the "Products" model contains all the items they sell. If you enter the Products menu, you are viewing the products model. A sales manager needs access to the sales orders model, while the warehouse keeper only needs the products and stock model. At Ganemo, we implement these permissions precisely so each role sees only what is necessary.
Record is a specific instance of a model. For example, the contact "Abigail Peterson" is a record in the contacts model. The order "S0026" is a record in the sales orders model.
Practical example: If a salesperson should only see their own orders, we are talking about restricting records within the orders model. Not all orders, only those where the salesperson is the current user. At Ganemo, we configure record rules so each salesperson sees only their own orders, avoiding exposure of other people's commissions.
Field is each piece of data within a record. For example, in order S0026, the "Salesperson" or "Date" field. Fields are the columns of the table.
Practical example: Imagine that in an order record, the "Commission" field should only be visible to the manager. With field rules, we can hide that field from salespeople. Ganemo helps you define which fields to show based on the user's profile.
The four basic operations: CRUD
With any record you can only do four things: Create, Read, Update (edit) and Delete. In English: Create, Read, Update, Delete (CRUD). All of Odoo's security revolves around these four operations.
Create: when you click "New" to add a record.
Practical example: Only users in the "Sales" group can create new orders. If a warehouse user tries to create an order, Odoo prevents it. We configure access rights on the orders model so that only certain groups have create permission.
Read: viewing existing records. It is the most common operation.
Practical example: A salesperson can only read their own orders, not those of others. This is achieved with a record rule that filters by the "Salesperson" field equal to the current user. Ganemo implements these rules easily.
Update: modifying an existing record.
Practical example: A salesperson can edit the price of an order, but not modify the maximum discount. We configure field-level access rights to restrict updating certain fields.
Delete: removing a record.
Practical example: Only managers can delete orders. If a salesperson tries to delete an order, Odoo blocks it. With record rules, we can prevent unauthorized users from deleting records.
Think with me: Is it a model or a record?
Reinforce your learning: "Products" in general is a model. "Conference Chair" is a record within that model. "Category Office Furniture" is a field within that record. Understanding this difference is key to configuring permissions. If you want everyone to see the product list, you configure permissions at the model level. If you want them to see only active products, you use a record rule.
At Ganemo, our experts guide you in configuring these concepts so your team works with exactly the right and necessary information, without security risks.
How does Odoo know who is who?
The real question every company asks is: How does Odoo know that Ana, the salesperson, can touch the orders and the warehouse keeper cannot? This is answered with users and groups. In the next article we will see how managers always end up asking for "each person sees their own". With Ganemo, that request becomes reality.