01
Hide Create / New button
The New button vanishes from list, kanban and form views. The user can still open and read existing records, but cannot start a new one from the UI.
hide_create_button
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1033 |
| Technical Name |
user_ui_access_control |
| License | OPL-1 |
| Website | https://erpoxa.com/ |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 1033 |
| Technical Name |
user_ui_access_control |
| License | OPL-1 |
| Website | https://erpoxa.com/ |
▶ Live demo · 30 s loop
The whole module in 30 seconds
Cover panel · four toggle groups · six before/after captures · common scenarios — captured against a real Odoo instance.
Every toggle is shown in detail with its own annotated screenshot further down the page.
🚀 Live Demo — login: demo / demo
User UI Access Control
Lock down the Odoo web client per user. Hide Create, Delete, Export, Print, Duplicate, Archive and the Actions menu. Hide the chatter and search filters. Make whole forms read-only. Disable developer mode. All from a single panel on the user form.
Odoo
Per-user toggles
16 features
Zero configuration
Try Demo
Test this module instantly
You can explore all features using the demo account. No setup required.
🚀 Live Demo
Demo credentials
Username: demo Password: demo
All toggles live on the user form — grouped by area: Control Panel, Form & Search, Field Widgets, Developer.
What it does
Sixteen independent toggles on the user form let you hide UI affordances per user — without touching access rights, security groups, or view inheritance.
+
Hide Create / New
Removes the New button on list, kanban and form views.
⚙
Hide Actions menu
Hides the entire Actions cog or selectively removes entries.
🖨
Hide Print menu
Removes the Print dropdown from the control panel.
🗃
Hide Archive
Removes Archive / Unarchive entries from the Actions menu.
🔒
Lock forms readonly
Forces every form view into read-only for the user.
▯
Hide form header buttons
Hides Send, Confirm, Create Invoice, Cancel, etc.
💬
Hide chatter
Removes messages, log notes and followers from form views.
🔍
Hide search filters
Hides the Filters / Group By / Favorites dropdown.
🔗
Field-widget controls
Hide "Create and edit" and Internal Link on Many2one fields.
≡
One2many lockdown
Hide "Add a line" and the per-row delete icon.
⚙
Disable debug mode
Strips ?debug= from URLs and removes Technical menu.
★
Per-user, no groups
Configured directly on the user form — no security groups required.
Every feature, with a screenshot
Each toggle below maps one-to-one to a checkbox on the user form, grouped by panel area. Tick it — the affordance disappears for that user on next login.
Control Panel
Hide the buttons and menus at the top of every list, kanban and form view.
02
Hide the Actions cog menu
Hides the entire Actions dropdown — both the Action and Print sections. Use this when you want to lock down every batch operation in one toggle.
hide_actions_button
03
Hide the Print dropdown
Removes only the Print section, leaving Action entries available. The user can still operate on records but cannot print or export reports.
hide_print_button
04
Hide the Export entry
Removes only Export from the Actions menu. Useful when you want to allow archive or duplicate but block bulk data export.
hide_export_button
05
Hide the Duplicate entry
Removes Duplicate from the Actions menu so users cannot clone records to bypass naming or numbering rules.
hide_duplicate_button
06
Hide the Delete entry
Removes Delete from the Actions menu. Combined with archive lockdown, this gives you a UI that can read and edit but not destroy records.
hide_delete_button
07
Hide Archive / Unarchive
Removes Archive and Unarchive entries from the Actions menu, even when the model supports the active flag — useful when archiving is reserved for managers.
hide_archive_button
Form & Search
Lock down form editing, header buttons, the chatter sidebar and the search filters dropdown.
08
Force every form into read-only
Makes the entire user experience read-only. Every form view opens locked — no field is editable. Independent from Odoo access rights, so a write-capable user can view records without accidentally changing them.
force_form_readonly
09
Hide form header buttons
Removes the row of action buttons at the top of form views (Send, Confirm, Create Invoice, Cancel, Validate, etc.). The user can still view and edit fields but cannot trigger workflow transitions.
hide_form_header_buttons
10
Hide the chatter
Removes the messages, log notes and followers panel on every form view. Cuts visual noise for restricted users and prevents them from posting messages or following records.
hide_chatter
11
Hide search filters dropdown
Removes the Filters / Group By / Favorites dropdown from the search bar. The plain text search box stays usable so the user can still find records.
hide_search_filters
Field Widgets
Trim the inline shortcuts on Many2one fields and one2many tables.
12
Hide "Create and edit…" on Many2one
Removes the inline Create and edit… option from Many2one dropdowns so users cannot spawn new related records from inside another form — they must go to the proper menu.
hide_m2o_create_edit
13
Hide the Internal Link button
Removes the small Internal Link arrow that lets a user jump from a Many2one field to the linked record. Stops side-channel navigation into models the user shouldn't browse.
hide_m2o_internal_link
14
Hide "Add a line" on one2many
Removes Add a line / Add a Product on one2many and many2many fields. Existing rows stay editable, but the user cannot append new ones.
hide_one2many_add_button
15
Hide the per-row delete icon
Removes the trash icon at the end of each row in one2many and many2many tables. Combine with #14 for fully locked-down line tables.
hide_one2many_delete_button
Developer
Block developer mode entirely — URL parameter, debug menu, and the Technical settings menu.
16
Disable developer mode
Prevents the user from activating developer mode — strips ?debug= from URLs, blocks the debug menu, and removes the Technical menu. Stops curious users from poking the internals.
disable_debug_mode
Common scenarios
Recipes you can apply in one minute. Each one is a small group of toggles that creates a recognisable, well-scoped user profile.
🔐
Auditor — read everything, change nothing
Open every record but cannot modify, create, archive or delete anything.
force_form_readonly · hide_create_button · hide_delete_button · hide_archive_button · hide_form_header_buttons · hide_one2many_add_button · hide_one2many_delete_button
👤
Sales agent — quotes only, no exports
Can create and edit sales orders, but cannot export the customer database or duplicate documents.
hide_export_button · hide_duplicate_button · hide_archive_button · hide_m2o_create_edit · disable_debug_mode
👾
Kiosk — ultra-minimal UI
Front-desk user sees only the bare essentials. No filters, no chatter, no actions, no developer hooks.
hide_actions_button · hide_search_filters · hide_chatter · hide_form_header_buttons · hide_create_button · disable_debug_mode
🎬
Demo account — safe playground
Prospects can click around without breaking anything — no delete, no archive, no developer mode, no data export.
hide_delete_button · hide_archive_button · hide_export_button · hide_duplicate_button · disable_debug_mode
⚙
Operator — lines protected
Warehouse / production operator can update header fields but cannot add or remove lines on orders.
hide_one2many_add_button · hide_one2many_delete_button · hide_m2o_create_edit · hide_form_header_buttons
👨
Junior staff — no side-channels
Block the easy ways to navigate or escape into models that aren't part of the daily job.
hide_m2o_internal_link · hide_m2o_create_edit · disable_debug_mode · hide_search_filters
How to install
- Install the module from
Apps → search "User UI Access Control" → Activate. - Open a user at
Settings → Users & Companies → Users. - Switch to the Preferences tab and scroll to UI Access Control.
- Tick the toggles you want for that user, then Save.
- Ask the user to log out and back in — the flags are read once per session.
Full feature reference
| Field | Effect |
|---|---|
| hide_create_button | Hides the New / Create button on list, kanban and form views. |
| hide_actions_button | Hides the entire Actions (cog) menu — both Action and Print dropdowns. |
| hide_print_button | Hides the Print dropdown in the control panel. |
| hide_export_button | Removes the Export entry from the Actions menu. |
| hide_duplicate_button | Removes the Duplicate entry from the Actions menu. |
| hide_delete_button | Removes the Delete entry from the Actions menu. |
| hide_archive_button | Removes Archive and Unarchive entries from the Actions menu. |
| force_form_readonly | Forces every form view into read-only — independent of access rights. |
| hide_form_header_buttons | Hides the action buttons in the form header (Send, Confirm, etc.). |
| hide_chatter | Hides the chatter (messages, log notes, followers) on form views. |
| hide_search_filters | Hides the Filters / Group By / Favorites dropdown on the search bar. |
| hide_m2o_create_edit | Hides "Create and edit…" in Many2one field dropdowns. |
| hide_m2o_internal_link | Hides the Internal Link button next to Many2one fields. |
| hide_one2many_add_button | Hides "Add a line" / "Add a Product" in one2many and many2many fields. |
| hide_one2many_delete_button | Hides the per-row delete icon in one2many and many2many fields. |
| disable_debug_mode | Disables developer mode — strips ?debug= from URLs and removes the Technical menu. |
Compatibility & notes
- Odoo version: 19.0 (Community & Enterprise).
- Dependencies:
base,web,mail. - License: OPL-1 (Odoo Proprietary License v1.0).
- Behaviour: the toggles are read from the session at login. Users must log out and back in for changes to apply.
- Scope: this module changes the web client UI only. It does not alter access rights or record rules — pair it with normal Odoo security for defense in depth.
DEVELOPMENT SERVICES
Custom Odoo development by Erpoxa
We're an Odoo-focused team. Bring us your weirdest workflow — we'll ship it cleanly.
🛠️
Custom modules
From single-screen wizards to full vertical solutions tailored to your industry.
🔄
Migration & upgrades
Move from Odoo 14/15/16/17 to 19 with zero data loss and a tested cutover plan.
🤖
AI integrations
OpenAI, Claude, Gemini and on-prem LLMs — wired into Odoo's standard models.
🔌
Third-party APIs
Payment gateways, shipping providers, government portals — plumbed in cleanly.
🎨
Themes & UX
Brand-faithful website themes and backend skins that don't break on upgrade.
🚀
Hosting & DevOps
Self-hosted Odoo on your servers — backups, monitoring, SSL, blue/green deploys.
CONTACT US
Built & supported by Erpoxa
An Odoo consultancy focused on scalable AI-powered modules and bespoke integrations. We answer fast and ship clean code.
🌐
Website
All apps, docs & portfolio
erpoxa.com
⏱ Typical response time:
< 8 business hours · Mon–Fri · GMT+3
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