Compliance: investigate actions with Audit Logs

Filter operations by period, user, activity and result, and export your company's records.

Illustration of a library and a team sharing knowledge.
Concept illustration · Knowledge that becomes the ability to act.

Filter operations by period, user, activity and result, and export your company's records.

How to use it

Open Compliance in Admin with tenant-configuration viewing permission. Select the period, user, activity and status. Use the trace identifier when working with support. In Alerts, select activities, results and recipients for email notifications.

Limits and prerequisites

Records cover instrumented HTTP operations and conversation reads in Admin. They do not capture every direct database change or job. Pending is not success; a 202 response means acceptance. There is no historical backfill. Logs do not store request bodies or credentials.

Validate in your operation

Perform a test action, locate its event and verify user, resource and result. Also validate alert delivery. Capture requires the corresponding environment update and appropriate permissions.

Availability

Feature identified in the platform code in October 2026. Availability depends on the deployed version, permissions and environment connectors. Contact Zild if it is not visible yet.

Documentation reviewed: 2026-10-28.

Read the announcement