Delete Guard

Block deletion model by model, reserve it for a few groups, and keep a record of every deletion.

A deletion leaves nothing behind: the record disappears, and its chatter with it. Odoo only offers one global right per model, granted or denied once and for all in the access rights β€” with no possible exception, no explanatory message, and not the slightest record of what was deleted.

What it adds

Real screenshots

1. Two models, two regimes

Contacts remain deletable, but every deletion is logged; contact tags, on the other hand, are locked for everyone.

List of deletion rules: Contact in "Allow, but log" mode, Partner Tags in "Forbid, except for allowed groups" mode

2. The refusal, as the user reads it

An administrator tries to delete a tag: the deletion is stopped and the message is the one written in the rule. The guard makes no exception for the administrator.

Odoo error dialog showing the custom message "Une Γ©tiquette de contact ne se supprime pas : archivez-la." (a contact tag cannot be deleted: archive it) after a deletion attempt

3. What actually disappeared

Three deleted contacts, with their ID and their name at the time of deletion β€” the only two pieces of information that can no longer be recovered afterward.

Deletion log: three contacts deleted by Claire Morel, with date, ID and record name

Why adopt it

Going further

To go beyond deletion and restrict what each person sees, the OdooSkills range includes some fifteen access-restriction modules β€” by sales team, by department, by project, by accounting journal, by warehouse. Full catalog: apps.odooskills.com.

License LGPL-3 β€” compatible with Odoo 19.0 Community and Enterprise. Support: apps@odooskills.com.