Advanced Access Control & UI Restrictions | Hide Chatter, Developer Mode, Buttons, Menus and Actions | Security Policy Manager
by TechUltra Solutions Private Limited https://www.techultrasolutions.com/$ 45.00
Advanced Access Control & UI Restrictions | Hide Chatter, Developer Mode, Buttons, Menus and Actions | Security Policy Manager
Advanced Access Control & UI Restrictions extends Odoo's standard security framework by
providing a centralized policy-based system for managing user permissions, interface
visibility, and operational restrictions. Organizations can create flexible access policies
that control what users can view, modify, export, print, or access throughout the system.
The module goes beyond traditional access rights by offering granular control at multiple
levels, including models, fields, menus, buttons, notebook pages, and system actions.
Administrators can configure restrictions for specific users or groups, helping
organizations enforce internal policies, simplify user interfaces, and protect sensitive
business information.
With support for field-level visibility, read-only controls, menu restrictions, export
limitations, duplicate prevention, and developer mode blocking, businesses can reduce
unauthorized access while improving operational governance. The module also helps create
cleaner and more focused user experiences by hiding unnecessary options from selected users.
Designed for organizations that require enhanced security, compliance, and role-based access management, this solution provides a powerful yet flexible framework for controlling user activities while maintaining seamless integration with standard Odoo functionality.
Advanced Access Control & UI Restrictions | Hide Chatter, Developer Mode, Buttons, Menus and Actions | Security Policy Manager
Product Overview
▶ Watch Module Demo
See how Advanced Access Control & UI Restrictions | Hide Chatter, Developer Mode, Buttons, Menus and Actions | Security Policy Manager works.
Features
Create centralized access policies for users and groups.
Control create, read, write, and delete operations.
Configure fields as hidden, read-only, or required.
Hide menus, form buttons, and notebook pages.
Restrict data export and duplication actions.
Make records read-only for selected users.
Hide chatter and communication history when required
Prevent access to developer/debug mode.
Restrict sensitive system actions and operations.
Log restricted actions and access violations.
Configuration
Support
FAQs
Mitchell user Configuration
After Install Module, navigate to Setting -> Users & Companies ->
Users
Here, you can see that the Mitchell user has Advanced Access Control -
Manager permissions, which allow it to bypass or ignore active policies.
Marc user Configuration
Navigate to Settings -> Users & Companies -> Users
Here, you can see that the Marc user has not been granted Advanced Access Control - Manager permissions.
Advanced Access Control Menu
Navigate to Setting -> Technical -> Advanced Access Control
Here, you will find two sections: Policies and Audit Log.
In Policies, you can define access control rules for users or groups.
In the Audit Log, you can view all log entries generated when a policy
denies an operation (i.e., model-level rules from this module), provided
that Audit Denials is enabled in the policy configuration.
Marc User Policies - Global Read-only Configuration
Here, you can see that Global Read-Only has been selected for the Marc user, and Audit Denials is enabled for logging purposes. With the Global Read-Only option applied, the Marc user system becomes entirely read-only. This means Marc can view records but cannot create, modify, or delete records in any models.
Marc User - Cancelling Sale Order
As you can see the Marc user attempts to cancel a sales order but receives a validation error due to Global Read-Only policies.
Marc User Policies - Global Hide Chatter Configuration
With the Hide Chatter option applied, the Chatter box will be hidden for the Marc user across all models that include Chatter functionality.
Marc User Policies - Chatter Box After Configuration
Here, you can see the Chatter box is hidden in sale order model.
Marc User Policies - Disable Developer/Debug Mode Configuration
With the Disable Developer/Debug Mode option applied, the Marc user will not be able to access or use Developer (Debug) Mode in the system.
Marc User Policies - Disable Developer/Debug Mode Before & After Configuration
Here, you can observe the difference in the header before and after applying the Disable Developer/Debug Mode configuration. Before enabling this option, the debug option is visible. After applying the configuration, the debug option is hidden.
Marc User Policies - Disable Import Configuration
With the Disable Import option applied, the Marc user will not be able to Import data into the system.
Marc User Policies - Disable Import Before & After Configuration
Here, you can observe the difference in the setting before and after applying the Disable Import configuration. Before enabling this option, the Import option is visible. After applying the configuration, the Import option is hidden and only Export option is visible.
Marc User Policies - Disable Export Configuration
With the Disable Export option applied, the Marc user will not be able to Export data into the system.
Marc User Policies - Disable Export Before & After Configuration
Here, you can observe the difference in the setting before and after applying the Disable Import configuration. Before enabling this option, the Export option is visible. After applying the configuration, the Export option is hidden and only Import option is visible.
Marc User Policies - Disable Archive/Unarchive Configuration
With the Archive/Unarchive option applied, the Archive and Unarchive actions will be hidden for the Marc user in the system.
Marc User Policies - Archive/Unarchive Before & After Configuration
Here, you can observe the difference in the Archive/Unarchive option before and after applying the Disable Archive/Unarchive configuration. Before enabling this option, the Archive/Unarchive option is visible. After applying the configuration, the Archive/Unarchive option is hidden.
Marc User Policies - Model/Report/Action Access Configuration
Here, you can see that the Sales Order model has been configured with restricted access. The PDF Quote report has been hidden, and the Mark Quotation as Sent and Generate a Payment Link actions have also been disabled for the Sales Order. In addition, the Duplicate functionality is not allowed for the Sale Order.
Marc User Policies - Model/Report/Action Access Before & After Configuration
Here, you can observe the difference in Report/Action Access for the Sales Order before and after applying the Model/Report/Action Access configuration. Before configuration this option, the PDF Quote, Mark Quotation as Sent, Generate Payment Link, and Duplicate actions were visible. After applying the configuration, these options are hidden in the Sales Order.
Marc User Policies - Field Modifiers Configuration
Here, you can see that the Sales Order model has been configured to hide the Payment Terms field when the sales order is confirmed.
Marc User Policies - Field Modifiers Before & After Configuration
Here, you can observe the difference in the sale order before and after applying the Field Modifiers configuration. Before configuration, the Payment Term field is visible. After applying the configuration, the Payment Term field is hidden.
Marc User Policies - Menu Hide Configurationr
Here, you can see that the Sales Order model has been configured to hide the Sale/Order Menu.
Marc User Policies - Menu Hide Before & After Configuration
Here, you can observe the difference in the sale order before and after applying the Menu Hide configuration. Before configuration, the Order Menu is visible. After applying the configuration, the Order Menu is hidden.
Marc User Policies - Hide Button Configuration
Here, you can see that the Sales Order model has been configured to hide the Cancel Button.
Marc User Policies - Hide Button Before & After Configuration
Here, you can observe the difference in the sale order before and after applying the Hide Button configuration. Before configuration, the Cancel Button is visible. After applying the configuration, the Cancel Button is hidden.
Marc User Policies - Hide Notebook Page Configuration
Here, you can see that the Sales Order model has been configured to hide the Order Line notebook page within the Sales Order form.
Marc User Policies - Hide Notebook Page Before & After Configuration
Here, you can observe the difference in the sale order before and after applying the Hide Notebook Page configuration. Before configuration, the Order Line Notebook Page is visible. After applying the configuration, the Order Line Notebook Page is hidden.
Access Audit Log
Here you can see Log rows when the policy denies an operation.
- We provide 90 days bug-free support related to our module.
- We provide 5 hours of free configuration support. Additional configuration or customization is billable.
- The support team is available from Monday to Friday 10:00 AM to 07:00 PM (IST).
- To create a ticket, send an email to support@techultra.in.
This module extends beyond basic permissions by controlling UI elements and actions like export, print, and buttons.
Yes, you can apply policies to individual users or groups.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1915 |
| Technical Name |
advanced_access_control |
| License | OPL-1 |
| Website | https://www.techultrasolutions.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