Hide Any Menu, Field, Button and Report - User & Group Wise
by Cerevantix Technologies https://www.cerevantix.com$ 29.01
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1300 |
| Technical Name |
cerevantix_hide_menu_field_button_and_report |
| License | OPL-1 |
| Website | https://www.cerevantix.com |
| Versions | 17.0 18.0 19.0 |
Hide any menu, field, button or report, per user
Tailor each user's interface without a developer. Hide menus, fields, buttons and reports by user or group, scope it per company, and preview the result before anyone logs in.
Odoo restricts the interface almost only by security group. Simplifying one person's screens or locking a sensitive field means new custom groups or a developer — and menu, field and report access all live in different places, with no way to scope any of it per company.
One no-code workspace to hide menus, fields, buttons and reports — by user or by group, scoped per company, and reversible with a single toggle. Preview exactly what a user will see before you apply it, with conflicts flagged and every change logged.
Everything you need to tailor the UI
Every capability below is implemented in the module.
Hide Menus & Submenus
Remove any menu or submenu from a user's navigation. Hiding a parent menu cascades to every menu beneath it, so whole apps disappear cleanly.
Hide or Lock Fields
Pick any field on any model and choose Hidden to remove it or Read-Only to show it while blocking edits — ideal for cost, margin or salary fields.
Hide Buttons & Actions
Remove form buttons a user should never press — confirm, validate, cancel or post — by their technical action name, so restricted operations simply vanish.
Hide Reports
Drop specific print actions from the Print menu for chosen users or groups, so data a person should not export is no longer one click away.
User & Group Targeting
Apply a restriction to individual users, to entire security groups, or both — choose the granularity that fits from the same screen.
Multi-Company Scoping
Scope any restriction to a single company or leave it global. A user's interface can differ by the company context they are working in.
Preview & Dashboard
See exactly what a chosen user will lose before you apply it, and open a per-user "What's Hidden" summary across menus, fields, buttons and reports.
Conflicts & Precedence
Overlapping restrictions are flagged inline with a clear rule: user-level wins over group-level, and Hidden beats Read-Only, so you always know which one applies.
Templates, Bulk & Audit
Start from Sales, Finance, HR or Warehouse role templates, apply or clone restrictions across many users at once, and review every change in the audit trail.
How it works
Create a Restriction
Name it, or start from a role template, and set the company scope.
Choose What to Hide
Add menus, fields, buttons and reports from one workspace.
Preview & Assign
Preview the result, then assign users and groups or bulk-apply.
Toggle & Audit
Switch restrictions on or off anytime; every change is logged.
See it in action
Real screens from the module, captured on Odoo 17.
Every restriction in one list, with users, groups and hidden menu, field, button and report counts at a glance.
A single restriction form: pick the menus to hide, with live counts for every element type.
Field restrictions with a per-field choice of Hidden or Read-Only.
Hide form buttons by their technical action name, such as Archive / Unarchive.
Reports selected here disappear from the Print menu for the targeted users and groups.
Assign the restriction to individual users, to security groups, or both.
Overlapping restrictions are detected and explained, with the precedence rule that decides which one wins.
Preview exactly what a user will not see — menus, fields, buttons and reports — before anything is enforced.
A full audit trail: who changed which restriction, what changed, and when.
Each user form gains a UI Restrictions tab and a "What's Hidden" summary button.
Ready-made role templates for Sales, Finance, HR and Warehouse to speed up first-time setup.
Open a template and click Create Restriction from Template to get an editable, enforceable copy.
Assign or revoke restrictions across many users at once, or clone one user's setup to others.
Frequently asked
Do I need to create new security groups?
No. You hide elements directly by user or by existing group from one screen — there is no need to build or maintain extra custom groups just to simplify an interface.
Is hiding reversible?
Yes. Every restriction has an Active toggle. Switch it off to restore the original interface instantly, without deleting or rebuilding your configuration.
What happens when restrictions overlap?
Overlaps are flagged on the form. The precedence is fixed and documented: a user-level rule wins over a group-level one, and within the same level Hidden takes priority over Read-Only.
Does it affect the administrator?
No. Restrictions only ever narrow access and never apply to the super-user, so an administrator can always reach the configuration and undo any change.
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.
Hide menus, fields, buttons and reports per user or group — no-code, reversible, and safe by design on Odoo.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1300 |
| Technical Name |
cerevantix_hide_menu_field_button_and_report |
| 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