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, or any user granted the activity.read ability.
You can also open a specific audit row directly with /activity/{id}. The activity page opens with that event detail already visible.
Views and filtering
The activity log supports different lenses depending on whether you are reviewing human-readable stories or technical diffs.
- Story View: The default view. It uses the Activity Statement Engine to convert raw events into clear, narrative sentences (e.g., "Moved department Engineering from Product to Operations").
- Grid View: A more technical layout that focuses on the raw audit event data and field-level diffs.
Filtering the trail
- Context: Filter by Live Baseline Only to see changes committed to your canonical state, or select a specific Scenario to review its isolated modeling history.
- Show Org Units: By default, the log focuses on high-level entities like Actors and Teams. Toggle this to include lower-level organizational unit plumbing.
- Auto Refresh (Live Tail): When active, the feed automatically polls for new changes every 15 seconds, making it ideal for monitoring large-scale imports or collaborative modeling sessions.
- Advanced Filters: Drill down by specific Kinds (e.g., modeling, security), Entities (e.g., Team, Actor), Actions (e.g., created, updated), or specific User IDs.
Narrative Interpretation
Orgonaut doesn't just show you raw database changes. The Activity Statement Engine interprets modeling events to provide context-aware narratives.
- Intelligent Verbs: Instead of generic "updated," you will see "Moved," "Reactivated," or "Set primary" based on the specific fields changed.
- Entity Context: Narratives automatically include related labels, such as the name of the department an actor was moved into.
- Tone and Icons: Events are color-coded (e.g., green for positive additions, red for destructive deletions) with descriptive icons to help you scan the feed quickly.
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 Baseline, 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.