Skip to Content

Advanced Access Control and UI Restrictions Manager | Hide Chatter, Developer Mode, Buttons, Menus and Actions

by
Odoo

$ 45.00

v 19.0 Third Party
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 1915
Technical Name advanced_access_control
LicenseOPL-1
Websitehttps://www.techultrasolutions.com/
Versions 16.0 17.0 18.0 19.0
You bought this module and need support? Click here!
Availability
Odoo Online
Odoo.sh
On Premise
Odoo Apps Dependencies Discuss (mail)
Lines of code 1915
Technical Name advanced_access_control
LicenseOPL-1
Websitehttps://www.techultrasolutions.com/
Versions 16.0 17.0 18.0 19.0

Advanced Access Control & UI Restrictions Manager | Hide Chatter, Developer Mode, Buttons, Menus & Actions

Take full control over user access like never before.
The Advanced Access Control & UI Restrictions Manager | Hide Chatter, Developer Mode, Buttons, Menus & Actions empowers businesses to go beyond traditional access rights by introducing a powerful, policy-driven system that controls not only data access but also user interface behavior and actions.
With this module, you can dynamically restrict what users can see and do across the system including menus, buttons, tabs, and critical actions like export, import, print, and duplicate.

Unlike standard access mechanisms, this solution provides multi-layer security enforcement across backend logic, frontend UI, and HTTP routes, ensuring that restrictions cannot be bypassed.
Whether you want to prevent data leakage, enforce strict operational workflows, or simplify the user interface for specific roles, this module gives you the flexibility and control you need.
Perfect for organizations that require advanced security, compliance, and user-level customization without complex configurations.

https://wa.me/message/VENRAJRHMSWEB1 OR
Email Us Skype Us

▶  Watch Module Demo

See how Advanced Access Control & UI Restrictions Manager | Hide Chatter, Developer Mode, Buttons, Menus & Actions works.

Watch Module Demo on YouTube
  • Advanced Access Management :

    - Create dynamic access policies per user or group
    - Apply restrictions on any model

  • UI-Level Restrictions :

    - Hide specific buttons in forms
    - Disable or remove notebook tabs (pages)
    - Control visibility of menus

  • Action Control :

    - Block Export functionality
    - Disable Import option
    - Restrict Print actions
    - Prevent record duplication

  • Smart Policy Engine :

    - Centralized configuration
    - Reusable policies across models
    - Real-time enforcement

  • User-Specific Permissions :

    - Apply rules to individual users
    - Not limited to groups

  • Data Protection :

    - Prevent unauthorized data extraction
    - Reduce risk of sensitive data leaks

1. 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.

2. 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.

3. 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.

4. 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.

5. 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.

6. 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.

7. Marc User Policies - Chatter Box After Configuration.

Here, you can see the Chatter box is hidden in sale order model.

8. 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.

9. 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.

10. 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.

11. 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.

12. 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.

13. 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.

14. 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.

15. 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.

16. 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.

17. 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.

18. 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.

19. 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.

20. Marc User Policies - Menu Hide Configuration.

Here, you can see that the Sales Order model has been configured to hide the Sale/Order Menu.

21. 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.

22. Marc User Policies - Hide Button Configuration.

Here, you can see that the Sales Order model has been configured to hide the Cancel Button.

23. 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.

24. 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.

25. 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.

26. 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.

How is this different from standard access rights?

This module extends beyond basic permissions by controlling UI elements and actions like export, print, and buttons.

Can I restrict actions for specific users only?

Yes, you can apply policies to individual users or groups.

Does it support multiple models?

Yes, you can configure policies for any model in the system.

Can I hide buttons and tabs from forms?

Yes, you can dynamically hide buttons and notebook pages.

Is it possible to disable export and print?

Yes, both export and print actions can be fully restricted.



Related Products


Our Apps 
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

  • The author can leave a single reply to each comment.
  • This section is meant to ask simple questions or leave a rating. Every report of a problem experienced while using the module should be addressed to the author directly (refer to the following point).
  • If you want to start a discussion with the author or have a question related to your purchase, please use the support page.