Currently, when a Timeline activity is updated via the API, the “Modified By” field is attributed to the user who last authorized the External Connection or updated the API key:
This creates significant friction for our team and end users:
- Auditing & Compliance: It is currently impossible to distinguish between a manual intervention by an Admin and an automated system update. For auditing purposes, these should be distinct.
- User Confusion: When automated updates are stamped with a human name, it creates the illusion of manual intervention, causing confusion for end users and forcing the Ops team to waste time explaining system behavior.
Context & Impact: In our specific use case, these Timeline activities contain highly sensitive information and we use an External Action to toggle a boolean to True once a dependent process completes.
Despite this being a minor, binary background update, the system stamps a human name on the record. This makes a routine automated handshake look like a manual manual override of sensitive data, which is misleading and complicates our debugging and oversight processes.
Requested Change: Please ensure system consistency by attributing these automated changes to "System Administrator" rather than the individual user who happens to hold the connection credentials. This would align the Timeline behavior with other automated system logs and provide the clarity required for sensitive data management.
