MODULES / CUSTOM

Attachment Chatter Log

Keep downloadable attachment evidence in chatter after removal, including the filename, actor and time.

Overview

Module idask_attachment_chatter_log
Version1.0.0
Who uses itAnyone who uses the screens listed below.
InstalledOn demand, from Settings → Modules. Anything it needs is installed with it.

How it links to other modules

  • Needs: Core
  • Works better with: no other module in particular
  • Needed by: no other module

A module that is needed cannot be turned off while the module that needs it is on.

Details

Attachment chatter log

Install ask_attachment_chatter_log from Settings > Modules before removing a file whose contents must remain available as evidence.

ASKERP already records attachment additions and removals with a filename, actor and timestamp. This addon completes the Odoo behavior by retaining the removed file and adding a Retained copy download to the removal event. It uses the same immutable timeline; it does not duplicate events or send email.

The ordinary download stops working after removal. The history download requires company membership, read permission, the installed and entitled addon, and access to the attachment's source module. Tenant RLS and composite foreign keys protect the retention index. Filenames render as text and downloads use attachment, nosniff, sandbox and private/no-store response headers.

Retention is recorded in the same transaction as removal. The UUID-named file stays in place, so rollback leaves the original download intact. Concurrent or repeated removals cannot produce duplicate removal events. Standard company backups include the retention rows and retained upload files.

Disabling hides history downloads without deleting evidence; reinstall restores access. Files removed while the addon is disabled follow normal deletion behavior and cannot later be recovered by installing it. The removal dialog explicitly says when a downloadable copy will remain.

Source inspected: ask_attachment_chatter_log/__manifest__.py, models and Odoo tests. ASKERP attachments are attached to a persisted record immediately, so Odoo's transient compose uploads, binary model fields and attachment reparenting have no equivalent path to log. Retention uses the original UUID file instead of creating a second binary attachment owned by a mail message.

Attachment Chatter Log | ASKERP Docs