Restrict Delete & Export — release notes

Every released version, what changed in it, and the date it went out. This page is generated from the module’s own changelog, which is the same file shipped inside security_access_restriction and rendered on its Odoo Apps Store listing.

Back to Restrict Delete & Export

18.0.1.0.5
Current6 September 2026
Changed
- Launch price: $29 to $19. The catalogue has no reviews yet, and an unknown vendor's price is the first objection a buyer has to get past. This is a deliberate, reversible move to buy the first sales and the first reviews, not a permanent valuation of the module. It is reviewed once there are five reviews across the catalogue, or at the end of 2026, whichever comes first.
18.0.1.0.4
6 September 2026
Changed
- The store listing now shows the product. 3 screenshots taken from a running Odoo 18, each captioned with what it shows.
- README, INSTALLATION, CONFIGURATION and USER_GUIDE all say Settings > Access Restrictions.
Fixed
- After installing, an administrator could not find the module. The menu hung off base.menu_security, which lives in Settings > Technical - and the Technical branch is gated on base.group_no_one, a group granted only while developer mode is on. An administrator who bought the module, installed it and never turned developer mode on saw no menu anywhere, and had no way to reach the rules. The root menu now hangs directly off Settings, so it appears as Settings > Access Restrictions on a normal database.
- Found by walking the Odoo 18 UI as a buyer would rather than by reading the XML: the app has no menu at all in the default state.
- The refusal message shown to a blocked user pointed at the same unreachable path. It now names the path that exists.
18.0.1.0.3
6 September 2026
Notes
- Documentation. No functional change.
- Added the three documents the module was missing against the house pattern: CONFIGURATION (the four global switches, the fields on a rule, why the design is an allow-list, and the 27 models that can never be restricted), FAQ (including the API limitation stated plainly rather than buried) and TROUBLESHOOTING.
- With 18.0.1.0.2 having moved the existing five documents into the module where the Odoo Apps Store reads them, this module now ships the full set of eight.
18.0.1.0.0
29 August 2026
Notes
- First public release. Targets Odoo 18.0, Community and Enterprise.
Added
- Restrictions
- Per-model rules covering five independent operations: delete, export, print, archive and duplicate.
- Allow-list semantics — once an operation is restricted, only the listed groups may perform it. Individual users can be added as exceptions.
- Custom refusal message per rule, with %(verb)s and %(model)s placeholders and a safe fallback when a placeholder is mistyped.
- Export restriction covers Odoo's standard CSV and Excel endpoints, checked before any data is read.
- Print restriction applies to the report's model, so it covers every report on that model including ones installed later.
- Archive restriction treats setting active to false as its own operation — the route users take when delete is blocked.
- Blocked-attempt log
- Who, when, which operation, how many records, a sample of ids, the display names for small selections, and the client IP.
- Written through a dedicated cursor so it survives the transaction rollback that follows the refusal.
- Immutable: not editable by anyone, including a Restriction Manager.
- Purged daily past a configurable horizon, in bounded batches.
- Grouped and pivoted by user, operation, model and date.
- Safety
- The superuser always bypasses; not configurable.
- Settings-group users bypass by default, switchable.
- A fixed Python-level deny-list of models that can never be restricted: res.users, res.groups, ir.model.access, ir.rule and others.
- The module's own records can never be restricted, so a rule is always reversible.
- Fails open — a fault in the module allows the operation rather than blocking work it was never configured to block.
- Configuration
- Two roles: Viewer and Manager.
- Settings panel with a master switch, the bypass toggle, and log retention.
- Nothing is restricted on install; the module changes no behaviour until a rule is created.
Technical notes
- Extends Odoo's base abstract model rather than patching core functions.
- Configuration cached per registry with automatic invalidation; a model without a rule costs one dictionary lookup.
- No eval, no raw SQL, no new HTTP routes, no external Python packages, no outbound connections.
- Depends only on base and web.
Verified
- 47 automated tests on a freshly created Odoo 18.0 database, including end-to-end coverage of the real export endpoint.
- Two findings surfaced during testing and were fixed: * a %(...)s placeholder in a view was being resolved as an Odoo external ID, breaking installation — the literal percent now escaped; * refusal logging was being written in the caller's transaction under test, which the rollback discarded — always written on a dedicated cursor now, so test and production exercise the same path.
Known limitations
- Exports through custom controllers or the XML-RPC/JSON-RPC API do not pass through Odoo's export funnel and are not blocked.
- Print restriction applies to the report's registered model.
- Raw SQL deletes are unaffected; nothing at the ORM level can prevent those.
- Archiving can only be restricted on models with an active field.
[18.0.1.1.0]
- Time-window rules — restrict deletion of records older than N days, so recent mistakes can still be corrected.
- Per-record conditions via a domain, e.g. restrict deleting only confirmed orders.
- Optional approval request: a blocked user can ask an allowed user to perform the operation, from the refusal dialog.
- A digest of blocked attempts for administrators.

Restrict Delete & Export — release notes

Back to Restrict Delete & Export

18.0.1.0.5
Current6 September 2026
Changed
- Launch price: $29 to $19. The catalogue has no reviews yet, and an unknown vendor's price is the first objection a buyer has to get past. This is a deliberate, reversible move to buy the first sales and the first reviews, not a permanent valuation of the module. It is reviewed once there are five reviews across the catalogue, or at the end of 2026, whichever comes first.
18.0.1.0.4
6 September 2026
Changed
- The store listing now shows the product. 3 screenshots taken from a running Odoo 18, each captioned with what it shows.
- README, INSTALLATION, CONFIGURATION and USER_GUIDE all say Settings > Access Restrictions.
Fixed
- After installing, an administrator could not find the module. The menu hung off base.menu_security, which lives in Settings > Technical - and the Technical branch is gated on base.group_no_one, a group granted only while developer mode is on. An administrator who bought the module, installed it and never turned developer mode on saw no menu anywhere, and had no way to reach the rules. The root menu now hangs directly off Settings, so it appears as Settings > Access Restrictions on a normal database.
- Found by walking the Odoo 18 UI as a buyer would rather than by reading the XML: the app has no menu at all in the default state.
- The refusal message shown to a blocked user pointed at the same unreachable path. It now names the path that exists.
18.0.1.0.3
6 September 2026
Notes
- Documentation. No functional change.
- Added the three documents the module was missing against the house pattern: CONFIGURATION (the four global switches, the fields on a rule, why the design is an allow-list, and the 27 models that can never be restricted), FAQ (including the API limitation stated plainly rather than buried) and TROUBLESHOOTING.
- With 18.0.1.0.2 having moved the existing five documents into the module where the Odoo Apps Store reads them, this module now ships the full set of eight.
18.0.1.0.0
29 August 2026
Notes
- First public release. Targets Odoo 18.0, Community and Enterprise.
Added
- Restrictions
- Per-model rules covering five independent operations: delete, export, print, archive and duplicate.
- Allow-list semantics — once an operation is restricted, only the listed groups may perform it. Individual users can be added as exceptions.
- Custom refusal message per rule, with %(verb)s and %(model)s placeholders and a safe fallback when a placeholder is mistyped.
- Export restriction covers Odoo's standard CSV and Excel endpoints, checked before any data is read.
- Print restriction applies to the report's model, so it covers every report on that model including ones installed later.
- Archive restriction treats setting active to false as its own operation — the route users take when delete is blocked.
- Blocked-attempt log
- Who, when, which operation, how many records, a sample of ids, the display names for small selections, and the client IP.
- Written through a dedicated cursor so it survives the transaction rollback that follows the refusal.
- Immutable: not editable by anyone, including a Restriction Manager.
- Purged daily past a configurable horizon, in bounded batches.
- Grouped and pivoted by user, operation, model and date.
- Safety
- The superuser always bypasses; not configurable.
- Settings-group users bypass by default, switchable.
- A fixed Python-level deny-list of models that can never be restricted: res.users, res.groups, ir.model.access, ir.rule and others.
- The module's own records can never be restricted, so a rule is always reversible.
- Fails open — a fault in the module allows the operation rather than blocking work it was never configured to block.
- Configuration
- Two roles: Viewer and Manager.
- Settings panel with a master switch, the bypass toggle, and log retention.
- Nothing is restricted on install; the module changes no behaviour until a rule is created.
Technical notes
- Extends Odoo's base abstract model rather than patching core functions.
- Configuration cached per registry with automatic invalidation; a model without a rule costs one dictionary lookup.
- No eval, no raw SQL, no new HTTP routes, no external Python packages, no outbound connections.
- Depends only on base and web.
Verified
- 47 automated tests on a freshly created Odoo 18.0 database, including end-to-end coverage of the real export endpoint.
- Two findings surfaced during testing and were fixed: * a %(...)s placeholder in a view was being resolved as an Odoo external ID, breaking installation — the literal percent now escaped; * refusal logging was being written in the caller's transaction under test, which the rollback discarded — always written on a dedicated cursor now, so test and production exercise the same path.
Known limitations
- Exports through custom controllers or the XML-RPC/JSON-RPC API do not pass through Odoo's export funnel and are not blocked.
- Print restriction applies to the report's registered model.
- Raw SQL deletes are unaffected; nothing at the ORM level can prevent those.
- Archiving can only be restricted on models with an active field.
[18.0.1.1.0]
- Time-window rules — restrict deletion of records older than N days, so recent mistakes can still be corrected.
- Per-record conditions via a domain, e.g. restrict deleting only confirmed orders.
- Optional approval request: a blocked user can ask an allowed user to perform the operation, from the refusal dialog.
- A digest of blocked attempts for administrators.

Restrict Delete & Export — release notes

18.0.1.0.5

Changed

18.0.1.0.4

Changed

Fixed

18.0.1.0.3

Notes

18.0.1.0.0

Notes

Added

Technical notes

Verified

Known limitations

[18.0.1.1.0]

Restrict Delete & Export — release notes

18.0.1.0.5

Changed

18.0.1.0.4

Changed

Fixed

18.0.1.0.3

Notes

18.0.1.0.0

Notes

Added

Technical notes

Verified

Known limitations

[18.0.1.1.0]