Skip to main content
The Verlauf tab on each agent’s detail page is a per-agent audit log. Every field-level change is recorded with the actor, timestamp, before/after values, and (for AI-driven edits) the chip indicating the Builder assistant was involved.

​
What gets logged

​
Dual avatars on AI-driven changes

When Pam (the Builder assistant) makes a change on your behalf, the history row shows:
  • Your avatar as the main face (you initiated the change).
  • Pam’s avatar as a small overlay in the bottom-right of your avatar.
  • A via Builder chip next to your name.
This makes it instantly clear which changes came from the AI versus changes you made directly in the form. The actor on the row is always you — Pam acts on your behalf, never as a separate entity.

​
Revert a change

Each history row whose change is the most recent for its field shows a ↶ Rückgängig button. Clicking it:
  1. Opens a confirm modal: “Diese Änderung an X wirklich zurücksetzen?”
  2. On confirm, writes the before value back to the agent.
  3. Records the rollback as a new audit row tagged Zurückgesetzt.
Only the latest change per field is revertable. Older entries don’t show the button because reverting an older change would either no-op (if it was already overwritten) or skip intermediate edits silently — both confusing. To roll back further, revert from the top of the list down.

​
What’s NOT in the history

  • Knowledge bucket content — adding/removing entries inside a bucket is logged on the bucket, not the agent. The agent only logs the link/unlink event.
  • Conversation messages — those live in the Konversationen tab. Audit is for the agent’s configuration, not its outputs.
  • Read events — opening the agent or running Pam without making changes leaves no audit trail. Only writes are logged.

​
Compliance

The audit log is retained indefinitely on the account. For GDPR / SOC2 contexts you can export the log via the conversations API (the activity endpoint is documented under the conversations group — same auth model).