Admin

Audit logs

Trace who triggered which change and when.

Updated: 2026-06-10

Audit logs record security- and process-relevant actions so decisions, changes and access can be traced later. They do not replace complete technical logging.

What is recorded

Typical entries contain actor, workspace, action, resource type, time and a limited summary. Sensitive content, passwords and complete tokens do not belong in audit data.

Review entries

Filter by period, user, client or action and compare suspicious changes with the business case. An audit entry proves an action was triggered, not automatically that it was correct.

Retention and protection

Restrict access to authorised roles, secure exports and define suitable retention. Gaps or unexpected deletion must be treated as a security risk.

auditlogs
Back to Help CenterContact support