One field needs a developer

Native Odoo has no UI for field level security. Making a single field read-only for one user means a custom module and a view inheritance.

Settings scattered everywhere

Groups, access rights, record rules and view attributes all live in different places, so nobody can answer "what can this user actually do?"

Hidden isn't blocked

Many access apps only hide buttons with CSS. The underlying operation still works, so the restriction is cosmetic rather than a real control.

Data walks out through Export

Any user who can read a list can usually export the whole thing to Excel, which is rarely what the business intended.

Multi-company blurs the lines

The same person often needs different permissions in different companies, and native groups apply globally to the user.

The fix: one rule, seven controls

One Access Rule record per group of users, seven tabs covering every dimension of Odoo access management, and enforcement that runs in the ORM rather than the browser.

Menus and Models

Hide any menu or submenu, and control create, edit, delete, archive, duplicate, import, export, reports and actions for each model.

Fields, Buttons, Tabs

Make individual fields invisible, read-only or required; hide action buttons, smart buttons, kanban buttons and notebook tabs.

Record-Level Rules

Write an Odoo domain and restrict read, create, edit or delete on just the records that match it: record rules without the XML.

User-Level Controls

Global read-only mode, hide chatter, disable developer mode, disable login, and remove security groups from specific users.

ORM Operation Blocking

Create, write and unlink are intercepted on Odoo's base model. A restricted user attempting a blocked operation receives an Access Error, regardless of whether the request came from the interface, an automated action, or a direct RPC call. Domain restrictions are evaluated here too, against the actual records being touched.

Per-User View Rewriting

The view architecture itself is rewritten before it reaches the browser: create/edit/delete/duplicate flags stripped from form, list and kanban views; fields marked invisible, readonly or required; buttons and notebook tabs removed; chatter deleted from the DOM tree. The user never receives markup they are not entitled to.

Client-Side Polish

Form, list and kanban controllers are extended so the remaining chrome behaves correctly: export, import, archive, duplicate, spreadsheet and Add Property controls are suppressed cleanly instead of throwing errors when clicked. This layer is about a tidy experience, not about security.

You Cannot Lock Yourself Out

Users in the Settings administrator group are exempt from every restriction at every layer. On top of that, the module's own configuration models are permanently excluded from restriction, so no rule can ever hide the tool you'd use to undo it.

Reversible in One Click

Every rule has an Active toggle. Switch it off and the restrictions lift immediately: no uninstall, no data loss, no cleanup. Test a policy on one user, then widen it once you're satisfied.

No Core Modifications

The module extends Odoo through standard inheritance and depends only on base, mail and web. Nothing in Odoo core is patched, so upgrades and other third-party apps are unaffected.

"Sales shouldn't see cost price"

Field Access → product.template → standard_price → Invisible. Gone from form and list for that team only.

"Auditors look, not touch"

Tick Read Only User. The whole database becomes view-only for them, enforced in the ORM.

"No exporting the customer list"

Tick Hide Export globally, or restrict it on res.partner only. Bulk download disappears.

"Suspend this account today"

Tick Disable Login. Sign-in is refused at the authentication layer while the user record and its history stay intact.

"Reps edit only their own leads"

Domain Access → crm.lead → a domain matching records they don't own → Restrict Edit and Delete.

"No internal notes on HR records"

Chatter Access → hr.employee → Hide Log Note, or hide the chatter panel on that model entirely.

What's Tracked

Each change is written to the rule's message history with the author and timestamp, useful evidence when an auditor asks who granted a permission and when.

Find Policies Fast

Built-in search filters let you answer questions like "which users are currently read-only?" or "who has login disabled?" without opening every rule. List, kanban and search views are all provided.

The Odoo user form also gains an Access Rules tab showing every rule currently applied to that person, the fastest way to answer "why can't this user do X?"

Standard Odoo model inheritance on base, ir.ui.menu, ir.model.fields and res.users. No core files are patched.

One rule header plus seven line models: menu, model, field, domain, button, chatter and group access.

The registry cache is cleared automatically whenever a rule is created, edited or deleted, so changes apply without a restart.

Domains are parsed with Odoo's safe evaluator, with the current user, company and company list available as context.

Two authenticated endpoints expose the effective configuration for the current user, used by the interface layer and available for your own extensions.

Distributed under LGPL-3. You can read the source, audit the enforcement logic yourself, and extend it for your own needs.

[Genuine customer quote]

[Genuine customer quote]

[Genuine customer quote]

How do I manage user permissions in Odoo without coding?

Create an Access Rule, assign the users, and configure restrictions across seven tabs. Everything that would normally need a custom module (hiding fields, buttons, tabs and menus) is done through the interface.

What is the difference between access rights and record rules in Odoo?

Access rights decide which models a user can read or write; record rules decide which records within those models. This module covers both: Model Access for the first, Domain Access for the second.

Are restrictions really enforced, or just hidden in the browser?

Both, and the coverage table above says which is which. Create, edit and delete (including read-only user and domain-based edit/delete limits) are intercepted in Odoo’s ORM and raise an Access Error however the request arrives. Menu, field, button and tab hiding is applied to the view on the server. A smaller set of conveniences (archive, reports, actions, spreadsheet, developer mode) is applied in the browser only. We publish the distinction rather than claiming everything is equally enforced.

Can I accidentally lock myself out of Odoo?

No. Settings administrators are exempt from every restriction, and the module's own models can never be restricted. Any rule can also be switched off with the Active toggle.

How do I give a user read only access in Odoo?

Tick Read Only User on the rule. Create, edit and delete are blocked system-wide for the assigned users, enforced in the ORM rather than by hiding buttons.

Does it work with multi-company Odoo databases?

Yes. Each rule can be scoped to selected companies, so one person can hold different permissions in different companies. Leave the company field empty and the rule applies everywhere.

How do I stop users exporting data from Odoo?

Use the global Hide Export toggle to remove it everywhere, or restrict export on individual models through Model Access when only certain data is sensitive.

Can I see which rules apply to a specific user?

Yes. The Odoo user form gains an Access Rules tab listing every rule currently applied to that person, the quickest way to diagnose why someone cannot do something.

Do permission changes leave an audit trail?

Yes. Access rules carry Odoo's chatter, and key fields are tracked, so every change is recorded with its author and timestamp on the rule itself.

Which Odoo versions and editions are supported?

Odoo 19.0, Community and Enterprise, on Odoo.sh or on-premise. Odoo Online is not supported because it does not allow modules containing Python code.

Will it conflict with my other Odoo modules?

It uses standard inheritance and depends only on base, mail and web, so it applies to any model in any app, including your custom ones, without patching Odoo core.

Is it a subscription?

No. One-time purchase, no per-user or per-rule fees, and no external services to pay for. The module is distributed under the LGPL-3 open source licence.