It would be great to have an audit trail to get more visibility on:
→ which user edited a workflow at what time
→ which user manually run a workflow (we can’t identify user for a test execution for now)
Mainly for security reason, but also in order to facilitate identifying which colleague made the last change that broke the workflow 
Hey @Yoann 
, Took a while for someone to answer this, but here we are!
I’ve been working on a similar problem — not exactly “who edited the workflow” but “who approved the execution and why.” The use case is the same though: when something goes wrong, you need to trace it back to a person and a decision fast.
The approach I took: a tamper-evident audit log where every action that passes through a policy gate is recorded with who approved it, what payload was approved, and a SHA-256 hash so you can prove the approved version is what actually executed. No more “I approved X but Y ran.”
On the rules side — you can write payload-aware policies. “Block any payment above $500 unless approved by a specific person.” Or “Auto-allow refunds up to $50, require approval above that.” Thresholds, allowlists, denylists, per-action-type rules. The audit log then shows you exactly which rule fired for each decision.
The “who broke the workflow” part is interesting — that’s more of an n8n-level feature (version history + user attribution on edits). What I’m building sits one layer down: once the workflow runs, who authorized each risky action inside it.
Happy to share more if this is the direction you’re headed., feel free to DM me