| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 448 |
| Technical Name |
access_rule_pro |
| License | OPL-1 |
| Website | https://www.linkedin.com/in/odoo-dev/ |
| Versions | 17.0 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 448 |
| Technical Name |
access_rule_pro |
| License | OPL-1 |
| Website | https://www.linkedin.com/in/odoo-dev/ |
| Versions | 17.0 18.0 19.0 |
Access Rule Pro
Configure different CRUD permissions per menu/action for the same model, from a single UI. This is a powerful architecture pattern usually implemented by custom code.
Same model, same users, but menu A can be read-only, menu B can allow create/edit/delete, and menu C can enforce a stricter domain. Access Rule Pro makes this logic practical, fast, and maintainable.
Why Access Rule Pro Is Special
Standard model-level security is not enough when different menus require different behaviors. Access Rule Pro adds a practical control layer based on menu action context.
Core InnovationOne configuration can contain multiple action lines: Menu A read-only, Menu B full CRUD, Menu C limited by company/department domain. Same model, same users, different control policy by menu. |
What Is Auto-GeneratedGenerated security group for selected users, generated model access rights from CRUD union, generated record rules from domains, and runtime view adaptation to hide create/edit/delete where disallowed. |
Configuration Preview
Real module UI where you configure action lines, record filters, and CRUD toggles.
How It Works
1. ConfigureChoose model, users, and menu actions with specific CRUD + domain rules. |
2. ApplyOne click creates or updates the generated group, access rights, and record rules. |
3. EnforceRuntime hook checks action context and applies UI restrictions consistently. |
Supported Domain Strategies
Ready-to-use presets for real business scenarios:
Full access, Own company, Other companies, Own department, Own company + Own department, Own company + Other departments, and fully custom domains.
Standard Odoo vs Access Rule Pro
| Capability | Standard Odoo | Access Rule Pro |
|---|---|---|
| Different CRUD per menu/action | No | Yes |
| UI configuration (no code) | No | Yes |
| Auto-generate groups/access/rules | No | Yes |
| Reset to draft with clean rollback | Manual | Built-in |
Need Help?
Full support included for setup questions, best-practice configuration, and custom requirements.
nguyentuann1004@gmail.comVersion: 17.0.1.0.0 | License: OPL-1 | Author: Tuan Nguyen Van
Compatible with Odoo 17 Community, Enterprise, and Odoo.sh
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