adding-activity-logging

Add ModelActivityMixin first in the model's bases, register the class name in the ActivityScope enum in both backend and frontend, then create a receiver module with a model_activity_signal receiver that calls changes_between and log_activity, imported in the app's ready() method.

Common causes are the receiver module not being imported in ready(), the write bypassing save() via QuerySet.update or bulk_create, only excluded fields changing, or transaction management deferring the write to a commit that never happened. Check each cause in order.

No. The mixin only hooks save() and delete(), so QuerySet.update(), bulk_create(), bulk_update(), and raw SQL are invisible to it. Those paths require manually reading before-values, building Change objects, and calling bulk_log_activity.

Pass using=router.db_for_write(Thing) to every log_activity and bulk_log_activity call, including inside the receiver. Without it, the audit row is written before the product row commits and survives its rollback.

Add secret fields to field_with_masked_contents so the change is recorded without the values. Use signal_exclusions for fields jobs touch every run, field_exclusions for bookkeeping fields, and field_name_overrides for user-facing names.