Odoo Security Guide: 2FA, Access Rights, Hosting and Hardening
Odoo security explained for Odoo 19 and 20: two-factor login, passkeys, access rights, record rules, hosting duties, patching and a hardening checklist.
"Is Odoo secure?" is the wrong first question. The framework is well defended, but your database is only as safe as its logins, permissions, hosting and patch level. Our Odoo consulting services often start with exactly that review.
Related service: Odoo implementation services — fixed-scope implementations with a named senior team.
This guide is for IT managers, CFOs and Odoo administrators on Odoo 19 or 20 who want a practical hardening plan. If you have not chosen hosting yet, read our comparison of Odoo Online, Odoo.sh and on-premise hosting first.
Is Odoo secure out of the box?
Odoo is secure out of the box at the framework level, but the default setup still leaves login policy, permissions and server hardening to you. Knowing where that line sits is the start of any Odoo security plan.
On its Odoo security page, Odoo says its framework blocks SQL injection through the ORM, escapes page content to stop cross-site scripting, and checks a security token on protected form posts. Access control runs on every request, not only in the user interface.
Passwords are stored with PBKDF2 and SHA-512 hashing, and Odoo staff cannot read them. The code is open source, so customers and researchers audit it, and Odoo runs a responsible disclosure program for reported flaws.
None of that helps if an administrator account has a reused password, if every salesperson can export the customer list, or if a custom module skips the access checks. Those parts are yours.
Who is responsible for Odoo security on each hosting option?

Odoo is responsible for the platform on Odoo Online and Odoo.sh, while on-premise puts the server, network, backups and updates in your hands. The table shows who does what.
| Security task | Odoo Online | Odoo.sh | On-premise |
|---|---|---|---|
| Server and operating system patches | Odoo | Odoo | Your team or host |
| Odoo security updates | Applied by Odoo | Sources updated weekly by default | You install new builds |
| Custom code review | Not applicable, no custom modules | You and your partner | You and your partner |
| Backups | 14 backups kept over 3 months | 7 daily, 4 weekly, 3 monthly | You schedule and store them |
| HTTPS and network defense | Odoo | Odoo, certificate issued for your domain | You: proxy, firewall, rate limits |
| Users, 2FA and access rights | You | You | You |
For Odoo Cloud, Odoo states that each customer has a dedicated database, that data is encrypted in transit and at rest with AES-256, and that backups are copied to at least three data centers. Odoo also lists CSA STAR Level 1 participation.
On Odoo.sh, the branch settings documentation says Odoo sources are updated weekly when the revision is set to Latest. If you pin a revision, it expires after three months, so a pinned project still has to move.
The last row never changes. Whatever you pay for hosting, nobody at Odoo decides who in your company can see payroll or approve a vendor payment.
How do you set up Odoo two-factor authentication and passkeys?
Odoo two-factor authentication is built in: each user enables it from the Security tab, and an administrator can enforce it for all employees or all users in Settings. This is the highest-value hardening step you can take in an afternoon.
The two-factor authentication documentation describes the flow. A user opens My Preferences, clicks Enable 2FA, confirms the password and scans a QR code with an authenticator app. To enforce it, tick the option under Settings, Permissions.
Enforcement has two scopes: Employees only, or All users. All users also covers portal users such as customers and vendors, so pick that when your portal exposes invoices, contracts or health data.
Odoo passkeys are the stronger option. The Passkeys module ships with Odoo 19 and 20 and installs automatically. Its description says a passkey replaces the username and password, and that a user who logs in with one is not asked for a second factor.
Plan recovery before you enforce anything. Odoo's documentation says an administrator must deactivate 2FA when a user loses the authenticator. On the Odoo forum, one admin was locked out of Odoo after a phone crash and had to ask about editing the database.
Keep two named administrators, each with their own second factor, so one can always reset the other.
What Odoo password policy and login controls should you use?
A sound Odoo password policy combines a minimum length, the built-in login cooldown, session timeouts and a regular check of signed-in devices. Odoo covers each one, but several are off or loose by default.
- Minimum length: the Password Policy module adds a Minimum Password Length setting under Settings, Permissions. Per the Odoo users documentation, the default value is 8.
- Login cooldown: new databases start with a cooldown after 10 failed logins, lasting 60 seconds. Administrators can tighten both values in System Parameters.
- Complexity rules: Odoo does not force mixed character classes by default and cites NIST guidance that such rules backfire. Length plus 2FA is the better trade.
- Timeouts: with the auth_timeout module installed, each group gets a Timeouts tab for inactivity and session limits, with an optional 2FA check on return.
- Devices: the Security tab of each profile lists devices and IP details for that login. Users can revoke any device they do not recognize.
- Single sign-on: Odoo documents sign-in with Google, Microsoft Azure and LDAP, which moves password rules to your identity provider.
One licensing point is also a security point. Shared logins destroy the audit trail, because every action shows the same name. Give each person their own user, and use portal or Light access where a full user is not needed.
How do Odoo access rights and record rules work?
Odoo access rights decide which models a group can create, read, update or delete, and record rules then filter which records inside those models each user can touch. Together they form two layers.
The access rights documentation lists the roles and the per-app levels you pick on a user form, such as User: Own Documents, User: All Documents and Administrator.
| Layer | What it controls | Example |
|---|---|---|
| Role | Internal user, Light, portal or public | A vendor gets portal access only |
| Group | A named bundle of permissions per app | Sales: User, Own Documents Only |
| Access right | Create, read, update, delete per model | Read invoices, but not delete them |
| Record rule | Which records, by a filter condition | Only the orders of my own team |
| Field access | Which fields a group can see | Hide cost price from sales staff |
Two details catch teams out. Access rights are additive, so a user in two groups gets the union of both. And groups inherit: Odoo's own example shows a Sales Administrator automatically receiving another app's permissions.
Record rules behave differently by type. Odoo's developer reference says global rules intersect, so each new one restricts further, while group rules unify, so each new one can widen access. A rule added to "fix" one user can open records to a whole group.
Superuser mode bypasses access rights and record rules entirely. Odoo's docs warn it can leave a database with no working administrator. Limit who holds the Settings right, and never use it for daily work.
For approvals, segregation of duties and the audit trail built on top of these layers, see our guide to Odoo internal controls.
What changes for Odoo user access rights in Odoo 20?
Odoo 20 keeps the same model of groups and rules for administrators, but adds a Light role and changes how developers declare security in modules. Both matter when you plan an upgrade.
The Light role is for staff who need little. Odoo's documentation says Light users can manage personal details, submit leave and expenses, use Planning, join Point of Sale sessions, read Knowledge articles and scan barcodes. They cannot open Sales, Purchase, Project or Accounting.
A Light user who is granted more access is upgraded to a full User automatically. That is useful least-privilege design, and it also changes your subscription count, so review group changes before you save them.
For developers, the Odoo 20 security reference describes a single access model that holds both the allowed operations and an optional domain. The Odoo 19 reference documents access rights and record rules as two models.
In practice, the security files in custom modules need porting and retesting at the upgrade. Ask your partner to test each role with a real login after the upgrade, not just as administrator.
How do you keep Odoo patched and supported?
You keep Odoo patched by staying on a version in standard support and by installing new builds regularly. Odoo's support policy makes this a hard line, not a nice-to-have.
Odoo's standard and extended support page says security updates are only provided during standard support, which covers the first three years after release. Extended support costs extra and does not add them.
| Version | Released | End of standard support |
|---|---|---|
| Odoo 20.0 | September 2026 | September 2029 (planned) |
| Odoo 19.0 | September 2025 | September 2028 (planned) |
| Odoo 18.0 | October 2024 | September 2027 (planned) |
| Odoo 17.0 | November 2023 | September 2026 |
Odoo 17 and older no longer receive security updates. If that is you, our post on the security risks of an unsupported Odoo version covers the exposure and the upgrade paths.
On-premise teams also need a routine for minor builds. Odoo's deployment guide tells you to keep installations updated by regularly installing the latest builds. Custom and third-party modules are outside Odoo's review, so they need their own code checks.
What does an Odoo on-premise hardening checklist look like?
An on-premise hardening checklist follows Odoo's own deployment guidance: lock the database manager, isolate PostgreSQL, put Odoo behind HTTPS and block brute-force attempts. These are Odoo security best practices, not optional extras.
Work through the security section of the Odoo deployment guide in this order:
- Master password: set a strong, random admin_passwd. Odoo warns a new on-premise install is open to anyone on the internet until it is set.
- Database manager: set list_db to False and use db_name or dbfilter. Odoo strongly recommends disabling the manager on any internet-facing system.
- Admin accounts: use unique logins and strong passwords, never admin/admin, and keep these accounts out of daily use.
- No demo data: demo databases contain default logins and passwords, so keep them off public servers, including staging.
- PostgreSQL user: the Odoo database user must not be a PostgreSQL super-user.
- HTTPS and proxy: run Odoo behind a web server with a valid certificate, limit request sizes, then enable proxy mode.
- Brute force: add rate limits and a tool such as fail2ban. Odoo's example bans an IP for 15 minutes after 10 failed logins in a minute.
- SSH and firewall: allow key-based SSH only, restrict access by VPN or trusted IPs, and deny outbound traffic by default.
- Backups: take daily backups of the database and filestore, and copy them to a remote server the Odoo host cannot reach.
Treat test copies as production. A staging database holds real customer and payroll data, so follow our Odoo staging environment checklist before anyone restores a copy.
Our DevOps services team builds and monitors this setup for clients who host Odoo themselves.
How do you secure Odoo integrations and API keys?
You secure Odoo integrations by giving each one its own user with minimal access rights and a short API key that you rotate on a schedule. An integration is a user that never sleeps.
Enabling 2FA has a side effect here. Odoo's two-factor module notes that 2FA blocks password-based RPC access for that user, so scripts must use API keys instead. That is a good thing: a key can be revoked without touching the password.
The Odoo 20 external API documentation says each key needs a description and a duration, is shown only once, and cannot last more than three months. Long-running integrations must rotate keys at least that often.
If a connected system is breached, speed matters more than neatness. Our guide to Odoo API key rotation after a breach gives the order of work.
How does Odoo data protection differ from security?
Odoo data protection is about what personal data you hold, where it sits and who may process it, while security is the set of controls that keeps it safe. You need both, and they are audited differently.
Security settings support privacy duties but do not replace them. Access rights limit who sees personal data. Hosting choice decides the region and the contract. Backups decide how long deleted data survives.
We cover those topics in separate guides, so this post stays on hardening:
- Privacy law: our Odoo GDPR compliance checklist covers hosting regions, the data processing agreement and subject requests.
- Recovery: our guide to Odoo disaster recovery by hosting type covers recovery targets and restore tests.
Which Odoo security controls matter most by industry?
The same Odoo security controls apply everywhere, but each industry has one or two that carry the most risk. Use the table to decide where to start.
| Industry | Main risk | Odoo control to set first | How iVentureTeam helps |
|---|---|---|---|
| Healthcare and MedTech | Patient or device data seen by the wrong role | Portal roles, record rules, 2FA for all users | Design and test role-based portals |
| Manufacturing | Costs, BOMs and supplier prices leaking | Field access on cost, group review | Map groups to shop floor and office roles |
| Retail and eCommerce | Many cashiers and a public website | Light users, per-person logins, HTTPS | Set POS access and harden the web tier |
| Professional services | Contractors seeing all projects and rates | Own Documents levels, portal access | Rework project and timesheet rules |
| Finance and holding groups | One user crossing company boundaries | Multi-company access, approval groups | Review company rules and duties |
How iVentureTeam helps with Odoo security

iVentureTeam treats Odoo security as part of running the system, not a one-time setup. We have delivered 150+ ERP projects across 35+ countries with 40+ Odoo specialists, led by a consultant with 13+ years in Odoo.
- Access review: we list every user, group and record rule, flag excess rights and shared logins, and propose a least-privilege map.
- Login hardening: 2FA enforcement, passkeys, password length, timeouts and a tested recovery path for administrators.
- Server hardening: the full deployment checklist, monitoring and backups for self-hosted Odoo.
- Custom code checks: review of custom and third-party modules for skipped access checks, raw SQL and unsafe public methods.
- Ongoing patching: our Odoo support services keep builds current and plan version upgrades before support ends.
Not sure where you stand? The free Odoo health check tool gives a first read on your version and modules.
Odoo security case study: Stigah BV
A Dutch medical device safety firm needed three audiences to work in one Odoo portal without seeing each other's data. This project is about access design, not server hardening, so read it for the role model only.
Stigah BV tracks medical devices and inspections across the Netherlands. Device records, inspection schedules and protocol authorizations sat in separate places, and inspection history had to stay retrievable for 7 years.
We built a role-aware Odoo portal in 10 weeks. Odoo access rights were configured so admins, standard users and inspection protocol users each see only what their role permits. Admins control invitations and profiles.
Inspection protocols carry per-protocol user permissions, and automation rules drive inspection statuses and schedules. The same portal works on desktops, tablets and phones. Read the Stigah medical device portal case study.
The bottom line on Odoo security
Odoo is as secure as the way you run it: the framework and Odoo's cloud are well defended, and the remaining risk sits in logins, permissions, custom code and patch level.
Start with 2FA for everyone and a review of who holds administrator rights. Then check your version against the support table, and, if you self-host, work through the deployment checklist. Most of this takes days, not months.
Ready to check how secure your Odoo database is?

Get a clear list of gaps and a plan to close them. Request an Odoo security and access review, call +91-90235-15208, or email business@iventureteam.com.
Frequently Asked Questions
Is Odoo secure?
+
The Odoo framework has built-in protection against SQL injection, cross-site scripting and CSRF, and hashes passwords with PBKDF2 and SHA-512. Your real exposure depends on logins, access rights, custom modules, hosting and whether your version still gets security updates.
Does Odoo support two-factor authentication?
+
Odoo includes two-factor authentication with authenticator apps. Each user enables it in the Security tab of their preferences, and an administrator can enforce it for employees only or for all users, including portal users, in Settings.
Does Odoo support passkeys?
+
Odoo 19 and 20 ship a Passkeys module that installs automatically. A passkey replaces the username and password at login, and Odoo does not ask for a second factor when a user signs in with one.
What is the difference between access rights and record rules in Odoo?
+
Access rights grant a group create, read, update or delete permission on a whole model, such as invoices. Record rules then filter which records in that model the user can reach, such as only their own team's orders.
Is Odoo Online more secure than on-premise?
+
Not by design, but it removes work. On Odoo Online, Odoo patches servers, applies security updates and runs backups. On-premise can be just as safe, but your team must handle hardening, HTTPS, patching and backups.
How often should Odoo be updated for security?
+
Stay on a version in standard support, because Odoo provides security updates only for the first three years after release. On-premise, install the latest builds regularly. On Odoo.sh, keep the revision on Latest for weekly updates.
Does Odoo encrypt data?
+
For Odoo Cloud, Odoo states that data is encrypted in transit over HTTPS and at rest with AES-256, in production and in backups. On-premise, encryption of disks, backups and traffic is set up by your own team or host.
How long can an Odoo API key last?
+
Odoo's external API documentation for Odoo 20 says a key cannot last more than three months, so long-running integrations must rotate keys at least that often. It recommends about one day for interactive use.
Can Odoo staff see my data?
+
Odoo says Helpdesk staff may access a cloud account when needed to investigate a support issue. They use dedicated staff credentials, cannot see your password, and limit access to what the issue requires.
Free Odoo support review
Need dependable Odoo support?
Tell us what's going wrong or what you need covered. We suggest a support plan that fits how you use Odoo.
Free, with no obligation. A senior consultant replies within 12 business hours.
Free Odoo tools
All tools- Odoo Health CheckVersion, modules, findings and upgrade cost
- Odoo App SelectorWhich apps you need, by industry
- Odoo Project EstimateIndicative cost and timeline in minutes
- Odoo Implementation Cost CalculatorImplementation cost and timeline, in minutes
- Odoo Migration Cost CalculatorVersion jump or legacy ERP, priced in minutes
Continue reading
Spreadsheets After ERP Implementation: Why Odoo Users Keep Excel
Why teams keep Excel after an Odoo go-live, the hidden risks of shadow spreadsheets, and a fix plan using Odoo 20 Spreadsheet, Dashboards and imports.
Odoo ERP Implementation in Saudi Arabia: ZATCA, Arabic, Cost, Timeline
Odoo ERP implementation in Saudi Arabia: Odoo 19 vs 20, ZATCA Phase 2 onboarding, Arabic invoices, GOSI and WPS payroll, hosting, cost and timelines.
Odoo Post Implementation Review: 30/60/90 Day Checklist and Template
Run an Odoo post implementation review at 30, 60 and 90 days: go-live checklist, six KPIs, Odoo 19 and 20 checks and a report template you can copy.
