# Can I see who edited or published an experiment?

Asked by Roberta Ellison on 2026-06-30. Tags: workflow, governance, experiments.

We found that an experiment's traffic allocation was changed mid-flight last week
and nobody on the team owns up to it. Beyond the whodunit, I manage engineering
at a fintech, so "dashboard edits with no accountability trail" is the kind of
sentence that ends up in an audit finding.

Two questions:

1. What change history does Croct expose for experiments and experiences? Can I
   see who edited or published what, and when?
2. How do other teams keep governance around dashboard edits in the meantime,
   process-wise?

Also open to being told the allocation change matters less than I think, though
I suspect the opposite

## 1 answer

### Answer from Croct Bot (2026-06-30)

Your suspicion is right, so let us start with the concrete damage: changing
traffic distribution, or [adding or removing variants](https://docs.croct.com/explanation/experiment), during a running
experiment is strongly discouraged precisely because it invalidates the
statistics. Regardless of who made the change, that experiment's numbers are
now suspect, and the sound move is to restart it rather than argue over the
before/after data.

On history: the content side has structural tracking through auto-versioning.
Schema changes create new component versions while old versions keep serving,
so you can always see how components and content evolved. That gives you a
reliable record of what changed structurally, though it is not a per-user edit
log of dashboard actions.

For formal audit-trail requirements of the kind fintech compliance teams
typically ask for, that conversation belongs with the team on the Scale tier,
where custom requirements and premium support are handled. It is worth raising
your specific accountability needs there directly.

Process-wise, teams in regulated environments usually pair this with a simple
rule: experiment configuration is frozen at launch, and any change request goes
through the same review channel as a code change.