The fastest way to start with a new ERP is to make everyone an administrator. It is also the fastest way to have a salesperson change a price after the invoice is posted, a cashier see the payroll, or a temporary employee export the whole customer list. Odoo has a detailed permission system; the job is to design roles that match how your company really works and keep them tidy as people join, move and leave.
FlexCode Middle East is part of FlexCode Systems GmbH, an Odoo Silver Partner. We implement Odoo, so Odoo is the system we describe, next to an honest look at the topic itself.
Key points
- Roles, not people. Define roles such as cashier or branch manager and assign people to them.
- Groups per app. Each app has levels such as user and administrator.
- Record rules filter rows. Salespeople see their own customers, branches see their own stock.
- Secure the login. Two-factor authentication and strong passwords for every internal user.
User types and groups
Odoo has internal users, who work in the back end and count toward the subscription, and portal users, such as customers and vendors, who only see their own documents. Internal users get access groups per application: for example Sales with own documents only, all documents, or administrator; Accounting with invoicing, accountant or adviser; Inventory with user or administrator.
| Role | Typical groups | Should not |
|---|---|---|
| Salesperson | Sales: own documents | Edit posted invoices or see costs |
| Cashier | Point of Sale: user | Give refunds without a manager |
| Storekeeper | Inventory: user | Validate inventory adjustments alone |
| Accountant | Accounting: accountant | Create vendors and pay them alone |
| Branch manager | Sales and Inventory for the branch | See other branches or payroll |
| HR officer | Employees and Payroll | Post accounting entries |

Record rules: who sees which rows
Groups decide which menus and actions a user has; record rules decide which records they see inside them. Standard rules already limit salespeople to their own opportunities when they have the own documents group. Custom rules can limit a branch user to their warehouse, a regional manager to their sales teams, or an HR officer to employees in one company.
- Use allowed companies and branches before writing custom rules.
- Test every role with a real user login before go-live.
- Keep custom rules few and documented; each one slows debugging later.
Groups of companies should read multi-company and intercompany in Odoo.
Segregation of duties and approvals
Auditors look for segregation of duties: the person who creates a vendor should not approve the payment, and the person who counts stock should not post the adjustment. Odoo supports this with separate groups, approval steps on purchases and payments, and the option to require a second person to validate bank account changes on vendors.
- Buyer creates purchase order
- Manager approves above limit
- Storekeeper receives goods
- Accountant posts the bill
- Finance manager approves payment
Approval steps are explained in purchasing in Odoo; for internal control over cash, see custody and petty cash in Odoo.
Securing logins and tracking changes
Every internal user should use two-factor authentication with an authenticator app, and administrators can enforce it for all internal users. A minimum password length, session timeouts for shared computers, and removing access on the day someone leaves close most gaps. Odoo tracks changes on key fields in the chatter, and logs logins with time and IP, so it is possible to see who changed what.
2FA
For every internal user
Day 1
Remove access when someone leaves
Quarterly
Review of users and roles
Logged
Changes on key fields
Wider security topics, including hosting and data protection laws, are covered in ERP security and data protection and Odoo hosting options.
FlexCode designs your Odoo roles
We map your organisation to roles, set groups and record rules, add approval steps auditors expect, enforce two-factor login and test every role before go-live.
Frequently asked questions
Can I stop salespeople seeing each other's customers?
Yes. Give them the own documents only group in Sales and CRM.
Can a branch user see only their branch?
Yes, with allowed branches or companies and record rules on warehouses.
Does Odoo support two-factor authentication?
Yes, with an authenticator app, and it can be enforced for internal users.
Can I see who changed a record?
Yes. Tracked fields show the change, user and time in the chatter.
Do portal users count as paid users?
No. Portal users such as customers and vendors are not billed as internal users.
Talk to us about how Odoo fits your business. Book a free call
Run invoicing, stock and accounts from one system.
FlexCode Middle East implements Odoo in Arabic and English for companies in Egypt, Saudi Arabia and the UAE.