Advance Access Right
The no-code security & access-control suite for Odoo — granular permissions, field-level security, and role-based access, all in one module.
Why This Module Is Essential
Native Odoo access rights (groups and record rules) can be complex and hard to visualize. Advance Access Right brings a "no-code" approach to security, letting you define highly specific rules — down to the field level — and group them into logical "Roles".
Everything You Need to Lock Down Odoo
A complete, no-code security toolkit — open and free for every Odoo team.
Role-Based Access Control (RBAC)
Stop assigning dozens of groups to every new hire. Build a Role (e.g. Sales Manager, Auditor) that bundles all needed groups and rules — then assign it in one click.
Temporal User Assignment
Perfect for temporary staff or auditors. Set a Start and End Date for access — the system automatically revokes permissions when the period expires.
Field-Level Security
Hide sensitive data (e.g. Cost Price) or lock critical fields (e.g. Credit Limit). Supports Invisible, Readonly, and Required attributes per user or role.
Conditional Field Logic
Make rules dynamic: "If Discount > 20%, then the Manager Approval field is Required." Apply field rules based on the record's own values.
UI Cleanup (Menus & Buttons)
Simplify the experience. Hide menus they don't use, remove buttons (like "Confirm" or "Cancel"), and hide entire notebook tabs to keep screens clean.
Advanced Data Filtering
Define domain record rules easily. Restrict users to records from their branch, their department, or any custom criteria you specify.
Granular Controls
The heart of the module — full control over the interface, data access, and functionality.
- Hide Menus: declutter by removing unused apps.
- Model Access: block Create, Edit, Delete, or Export per model.
- Field Options: make any field Invisible, Readonly, or Required.
- Conditional Access: "If X > 100, then Y is Required".
- Domain Access: advanced record rules to filter data rows.
- Chatter Access: hide internal notes, emails, or activity logs.
- Hide Buttons & Tabs: remove "Confirm" buttons or notebook pages.
- Search Panel: hide filters and grouping options.
Common Use Cases
The "Viewer"
A read-only role for directors or auditors who must see everything but change nothing. Use the Global Readonly toggle.
The "Junior Staff"
Hide the Delete and Export buttons on all models. They can create data, but never remove or leak it.
Focused UI
For warehouse staff, hide Accounting, Sales, and Website menus — a simple, undistracted interface to do their job.
Performance optimized: an intelligent caching layer stores computed access rights, so your system stays fast even with complex rules active.
Release Notes
Actively maintained. Every release documents what changed, what improved, and what was fixed.
Bug Fixes
- Hidden tabs and buttons are now correctly applied per user. View modifiers were previously computed inside Odoo's shared view-architecture cache, which carries no user identity. As a result, the first user to open a screen after a server restart determined what every other user saw — if that was an administrator, restricted users kept seeing the hidden tabs and buttons. Modifiers are now applied per request. This affects Hide Buttons & Tabs, Field Options, Conditional Access, and Readonly Mode.
- Rules no longer leak between models in embedded subviews. A rule targeting an order also matched identically named buttons and tabs inside the embedded order lines list. Each embedded subview is now evaluated against its own model.
- Configuration changes take effect immediately. Editing a rule no longer requires a server restart before the change becomes visible.
-
Buttons in list views are discovered again.
The discovery scan still looked for the legacy
treeview type, renamed tolistin Odoo 19. Existing records using the old name keep working. - Removed unreachable and broken internal code in the hide-buttons and chatter-validation logic.
Improvements
- Lower overhead for unrestricted users. A cached lookup of restricted models means users with no applicable rule never pay the cost of re-processing a screen.
- Better diagnostics. Problems while applying restrictions are now written to the server log instead of being silently ignored — while screens still never break because of a misconfigured rule.
Initial release for Odoo 19.
Scope of UI hiding: hiding buttons and tabs is an interface control, not a data-security boundary — the underlying records stay reachable through the ORM. For sensitive data, combine it with Field Options, Model Access, and Domain Access, which are enforced on the server.
Brought to You by Albirru Solutions
We released Advance Access Right as free and open-source software (LGPL-3). Use it, modify it, and ship it in your own projects — no license fee, ever.
Albirru Solutions is a Jakarta-based IT services company helping businesses run Odoo securely and efficiently.
Integrated IT Solutions for Enterprise
Credibility rooted in experience — end-to-end technology services under one partner.
Software Development
Custom apps, ERP & Odoo implementation, API integration, and Flutter mobile apps.
Cloud & Infrastructure
Cloud migration, high-availability design, server management, backups, and network design.
IT Managed Services
IT outsourcing, helpdesk support, 24/7 monitoring, maintenance, and procurement consulting.
Cybersecurity
Security audits, vulnerability assessments, firewall management, data protection, and training.
Need Help with Implementation?
The module is free — our expertise makes it work for you. Get professional Odoo implementation, customization, training, and support from Albirru Solutions.
Advance Access Right · Free & Open Source (LGPL-3) · © Albirru Solutions (Irwan Syah)
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 3930 |
| Technical Name |
advance_access_right |
| License | LGPL-3 |
| Website | https://www.albirru.com/ |
Please log in to comment on this module