Pause before every irreversible server action
Add a blocking confirmation dialog to any Odoo server action — with severity styling, group and threshold rules, and a full audit trail — all without touching the action’s own logic.
The problem
Server actions run the instant they are triggered from a button or the Actions menu — a single mis-click on a list of hundreds of selected records can delete, archive, or overwrite business-critical data with no ‘are you sure?’ moment in between.
The solution
Server Action Confirmation Box adds a governed pause in front of any server action. Mark it as sensitive, choose the wording and severity, and every confirm or cancel decision is written to an audit log — the underlying automation never changes.
Everything you need to gate risky actions
Every capability below is implemented in the module.
Blocking Confirmation Dialog
Intercepts a triggered server action and holds it until the user explicitly confirms, so nothing runs until intent is verified.
Clean Cancel
Choosing Cancel — or dismissing the dialog — aborts the action outright. No request is ever sent and no data changes.
Per-Action Toggle
Enable confirmation only on the server actions that matter, keeping routine automations friction-free.
Custom Message, Title & Labels
Write context-specific wording, dialog titles, and button labels per action so operators understand exactly what they are about to do.
Ready-Made Templates
Apply Delete, Archive, or Mass Update templates in one click instead of drafting confirmation copy from scratch.
Severity & Size Styling
Style each dialog as Info, Warning, or Danger and choose Small, Medium, or Large so an irreversible delete looks nothing like a routine confirm.
Bulk Enable & Disable
Select multiple server actions from the list view and apply or remove confirmation settings across all of them in a single wizard.
Group & Threshold Rules
Limit confirmation to selected user groups and to selections above a minimum record count, so trusted users and small operations are not interrupted needlessly.
Full Audit Log
Every confirm and cancel decision is recorded with the user, action, target model, and record count — turning the dialog into accountability evidence.
How it works
Mark the action
Open any server action and enable confirmation on its new Confirmation tab.
Configure or apply a template
Set the message, severity, size, and optional group or threshold rules — or pick a ready-made template.
Operators confirm before it runs
When the action is triggered, the dialog blocks execution until the user confirms or cancels.
Review the audit trail
Every decision lands in the confirmation log, with the user, outcome, and record count preserved.
Frequently asked
No sales fog. If your question isn't here, email us and we'll answer it the same way.
No. The confirmation layer intercepts execution in the web client before the action runs — your server action’s own code and automation logic are never touched.
Buy it on the Odoo App Store
Purchase, download and install directly from the official Odoo Apps Store — you'll always get the latest supported build.
Server Action Confirmation Box
A blocking confirmation dialog in front of any server action, with templates, severity styling and group or record-count threshold rules — every confirm and cancel audit-logged.
Buy on Odoo App Store