Disable Create and Edit on Many2one
Block quick-create and quick-edit on any Many2one field, reliably and generically, with group and user exceptions, a clear denial message, and an audit log of every blocked attempt.
Every Many2one field, Product, Vendor, Customer, invites staff to type a
new value and silently create a full record from a Sales Order line, a
Purchase Order, an invoice, or a stock move. Odoo's native
no_create/no_create_edit view attributes are
inconsistent across fields, easy to miss on one screen out of dozens, and
require a developer to configure — leaving master data full of
duplicate, incomplete records nobody meant to create.
Pick any model from one dedicated Settings screen and its quick-create and quick-edit options disappear everywhere that model shows up in a Many2one dropdown, no matter which app it lives in. Exempt specific groups or individual users, and blocked staff see a clear explanation instead of a confusing empty list — every denied attempt is logged for review.
Reliable, generic, and auditable
Every capability below is implemented in the module.
Restrict Any Model
Not limited to Product or Contact. Pick any model from the Restriction Rules screen and every Many2one field pointing to it is covered.
Blocks Create & Create-and-Edit
Hides the typed quick-create option and the "Create and edit..." popup together, so there is no back door left open.
Works Across Every App
One rule enforces the same restriction on Sales, Purchase, Invoicing, Inventory, and any other screen that references the restricted model.
Group-Based Exceptions
Exempt one or more security groups per rule, matching how Odoo access rights are already managed.
Individual User Exceptions
Exempt a single trusted user even when their group is restricted, for the cases group membership alone cannot express.
Dedicated Settings Screen
Configure every rule from Settings > Many2one Restrictions — no
developer mode and no technical ir.model menu required.
Clear Denial Messaging
Blocked users see a configurable, human-readable message in the dropdown itself, instead of a disabled button or a confusing blank "No records" state.
Audit Log of Blocked Attempts
Every denied attempt records the user, the restricted model, the field, the document it was attempted from, and the timestamp.
Consistent in Form, List & Kanban
The same restriction holds whether the field is reached from a form, an editable list row, or a kanban card — one enforcement point, not one per view.
How it works
Pick a Model
Choose the model to restrict, such as Product or Contact, from the Restriction Rules screen.
Set Exceptions
Add the groups or individual users who should keep the ability to create and edit.
Staff See a Clear Message
Restricted users get your configured explanation right in the dropdown, wherever the field appears.
Review the Audit Log
See exactly who tried to create or edit a restricted record, and when.
See it in action
Real screens from the module, captured on Odoo 17.
Every restriction rule in one list — restricted model, allowed groups, allowed users, and an active toggle.
A Contact rule with no exceptions and a custom denial message shown to every blocked user.
A Product rule that exempts the "Product Catalog Managers" group, so that team can keep creating and editing while everyone else is blocked.
The Blocked Attempts Log — who tried to create or edit a restricted record, which field, which document, and when.
An exempted user still sees "Create" and "Create and edit..." on a Sales Order line — exceptions work exactly as configured.
A restricted user typing an unmatched name into the Customer field sees the configured denial message — never a blank "No records" state.
The same restriction and the same clear messaging, on the Product field of a Sales Order line — one rule, every transactional screen.
Frequently asked
Does this only work on Product and Contact fields?
No. A restriction rule can target any model in the system. Product and Contact are the most common choices, but the Restriction Rules screen lets you pick whichever model you need to lock down.
Do I still need Odoo's native "no_create" view options?
No. The module enforces the restriction directly on the Many2one widget
itself, independent of each view's own no_create/
no_create_edit settings, so coverage does not depend on every
view being configured correctly.
Can I let a few people bypass a restriction?
Yes. Each rule has its own Allowed Groups and Allowed Users lists. Add a security group to exempt everyone in it, or add an individual user to exempt just them, even if their group is restricted.
What do blocked users actually see?
A clear, configurable message right inside the dropdown, in place of the create options or a blank "No records" state — so they know it is a permission boundary, not a bug. Every attempt is also written to the Blocked Attempts Log.
Get in Touch
Have questions or need customization? Every purchase includes 30 days of free support — we are here to help.
Visit Our Website
www.cerevantix.comExplore our apps, services, and portfolio.
Explore our other apps
A growing suite of Odoo apps.
Empowering growth through technology.
Reliable, generic Many2one create/edit restriction with group and user exceptions, clear denial messaging, and a full audit trail.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Lines of code | 272 |
| Technical Name |
cerevantix_disable_create_and_edit |
| License | OPL-1 |
| Website | https://www.cerevantix.com |
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module