Activity log and audit trail
The activity log gives you a factual record of structural change.
Use it to answer: what changed, when did it change, and who changed it?
Open it from the top-right profile menu under Activity at /activity.
The activity feed is visible only to roles that include activity access. By default that means tenant owner, admin, and manager roles.
You can also open a specific audit row directly with /activity/{id}. The activity page opens with that event detail already visible.
When to use it
- Scenario review before promotion
- Post-promotion validation
- Investigating unexpected structural outcomes
- Compliance and governance reporting
What to look for
For each change, check:
- entity type (actor, team, department, placement, etc.)
- action (created, updated, deleted, restored)
- before/after values for changed fields
- timestamp and actor identity
This lets you reconstruct decision context without guessing.
High-value workflows
Scenario readiness review
Before promotion, scan recent scenario activity to ensure:
- all intended edits are present
- no unintended edits were introduced
- critical entities were updated coherently
Promotion follow-up
After promotion, compare expected changes against activity history.
If something looks wrong in Live, use the log to isolate the exact change event.
Change narrative for stakeholders
Use activity records to produce a short factual summary:
- what was changed
- why it was changed
- what impact was expected
Tips for better traceability
- Use clear scenario names.
- Keep scenario scope focused.
- Avoid making unrelated edits in the same review cycle.
- Capture decision notes alongside scenario approval.
Common mistakes
- Treating the activity log as optional during reviews.
- Looking only at final state and skipping event history.
- Merging unrelated edits, which makes attribution harder.