Hide Delete Button — Global & Per-Model, with Audit
by Cerevantix Technologies https://cerevantix.com$ 34.00
Hide the Delete Button User by User
Remove Delete from list rows, form views and the Actions menu for the users and models you choose — globally or per model — while every blocked attempt is captured in a full audit trail.
Anyone with write access to a record can usually delete it too, and Odoo's native access rights are too coarse to carve out a simple no-delete rule without risking other permissions. One careless click on a sales order, invoice or contact destroys data that audits and daily operations depend on, and there is no record of who tried.
Hide Delete Button hides the Delete action wherever it appears and blocks it server-side too, so restricted users cannot delete through the UI, RPC, server actions or imports. Configure the restriction globally or per model, per user, apply it in bulk with templates, and review every blocked attempt in an audit log.
This app speaks your language.
Tell us the language your team works in and we translate this module for you, free of charge — so everyone works in the language they know best.
Request my free translation →No hidden fees. No subscription.
Everything you need to lock down deletion
Every capability below is implemented in the module.
Hide Delete Everywhere
Removes the Delete action from list rows, the form Actions (kebab) menu and kanban cards in one consistent restriction, so nothing is left exposed in a view the admin forgot about.
Real Server-Side Enforcement
Restriction is enforced on the model itself, not just in the UI, so a blocked user cannot delete a record through RPC calls, server actions or the import wizard either.
Global or Per-Model Scope
Choose whether a user is restricted from deleting everything, allowed to delete everything, or given an explicit allow-list or restrict-list of specific models — one app covers both scopes that competitors split across two products.
Reusable Policy Templates
Build named templates for roles such as Manager, Reviewer or Sales Rep, then assign a template to any number of users instead of configuring each person by hand.
Bulk Apply Delete Policy
Use the Apply Delete Policy wizard to roll a mode, scope or template out to many users at once, so onboarding a whole department takes one action instead of dozens.
Native CSV Batch Import
Import user, model and restriction-status combinations through Odoo's standard CSV importer for fast onboarding or large-scale policy rollouts.
Deletion-Attempt Audit Log
Every blocked delete attempt is recorded with the user, model, affected records, reason and timestamp, giving administrators the accountability evidence audits ask for.
Admin Notification on Blocked Attempts
Optionally send administrators an inbox notification the moment a restricted user tries to delete a record, so risky behaviour surfaces immediately instead of after the fact.
Master Switch & Unrestricted Group
A single settings toggle turns the whole restriction on or off, and an Unrestricted group gives trusted users, such as super administrators, an explicit escape hatch.
How it works
Turn it on
Enable the master switch in Settings and decide whether blocked attempts should also notify administrators.
Define policies
Create per-user delete permissions or reusable role templates with a global, allow-list or restrict-list scope.
Roll out at scale
Assign policies with the bulk Apply Delete Policy wizard or import them from a CSV file for larger teams.
Review the audit trail
Check the deletion-attempt log any time to see exactly who tried to delete what, and when.
See it in action
From per-user permissions and role templates to the audit log and the button disappearing in real time.
The Delete Permissions list shows every user's mode, scope summary, assigned template and active status at a glance, so admins can audit restrictions across the company in one screen.
Open any permission to set the mode, pick the allowed or restricted models, and see a chatter history of every change made to that user's restriction.
Policy templates package a mode and model scope under a named role, such as Manager or Sales Rep, so the same rule can be applied to many users.
Each template shows its scope and a user count stat button, making it easy to see how many people currently follow that policy before changing it.
Every delete attempt is logged with a blocked or allowed decoration, giving administrators a running record of who tried to remove what.
Drill into a single attempt to see the affected records, the reason it was blocked or allowed, and exactly when it happened.
The Apply Delete Policy wizard rolls a mode, scope or template out to a batch of users in one action, instead of editing each permission by hand.
A dedicated Settings panel holds the master on/off switch plus toggles for admin notifications and logging every attempt, not only blocked ones.
A Delete Security page embedded directly on the user form lets admins review or adjust one person's restriction without leaving the Users app.
Before: an administrator opens the Actions menu on a contact and sees the Delete option alongside Edit Properties, Duplicate and Archive.
After: the same Actions menu for a restricted user on the same record — Delete has disappeared entirely, while every other action stays available.
Frequently asked
Does this hide Delete in every view, or just one?
It hides Delete consistently in list rows, the form Actions (kebab) menu and kanban cards, and blocks deletion server-side too, so the restriction cannot be bypassed through RPC calls, server actions or imports.
Is the restriction global or per model?
Both, in the same app. Set a user's mode to restrict or allow everything, or give them an explicit allow-list or restrict-list of specific models — you choose the scope per user or per template.
What if a user belongs to a group that already grants delete rights?
Our restriction applies on top of native access rights. If a user is marked as restricted, Delete stays hidden and blocked even when their security groups would otherwise permit it.
Can we see who tried to delete something after being blocked?
Yes. Every blocked attempt is written to an immutable audit log with the user, model, affected records and timestamp, and you can optionally notify administrators the moment it happens.
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.
Empowering growth through technology.
Hide Delete Button gives Odoo administrators global and per-model control over who can delete records, backed by policy templates, bulk assignment and a full audit trail.
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
Discuss (mail)
|
| Lines of code | 747 |
| Technical Name |
cerevantix_hide_delete_button |
| License | OPL-1 |
| Website | https://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