Flow in System Mode? For a User with no CRED access to Object? → Audit Hole
🕵️‍♂️
If you follow the Principle of Least Privilege by using System Mode (Flow/Apex) to keep users restricted, you have likely created an Audit Hole.
The Paradox:
- The System authorizes the change: The DML succeeds in the background.
- The Identity is known: LastModifiedBy correctly captures the user’s name.
- The Audit is erased: Field History Tracking stays blank because the platform tethers auditing to the User's manual Permissions, not the System's authorization.
The "Permission Ransom": To get a single log entry, you are currently forced to grant manual "Edit" access to restricted profiles. This "fixes" the audit trail but destroys security by creating Leakage Points—suddenly, sensitive record names appear in Lookups and Related Lists across the entire Org.
The Fix: Decouple Field History from User Context. If the system is smart enough to authorize the DML, it must be smart enough to audit the change.
Stop sacrificing Security for Compliance. Vote/comment to bridge the gap: here is the Idea, to Enable Field History for System Mode DMLs Regardless of Object Permissions
