Skip to content

Audit log, export, and retention

Outcome

You will find who performed a project action, export a portable copy of project data, and configure retention without assuming that a saved value has already deleted anything.

Before you begin

  • The Audit Log tab is visible from Viewer by default, but an owner can raise its minimum role under Organization → Access control.
  • Export & Retention is admin-only.
  • Export before shortening a retention window. Retention deletion is not an archive and is not reversible from the UI.

Investigate an event

  1. Open Settings → Audit Log.
  2. Filter by actor email, exact action, From date, or To date.
  3. Select a row to expand its complete list-view record.
  4. Review the time, actor, action, resource, IP address, user agent, and metadata.
  5. Select Load more to continue beyond the first 50 results.
  6. Correlate the event with Activity and the external system.

The audit page is ordered newest first. The expanded UI record intentionally does not show every before/after state; the JSON export contains the fuller audit representation.

Export project data

  1. Open Settings → Export & Retention.

  2. Choose:

  3. Download JSON bundle for project entities and audit log in one file;

  4. Download entities CSV for a tabular entity-only export.

  5. Wait for the browser download and store it in an approved location.

  6. Open the file and verify the project, export timestamp, and expected sample records before treating it as a usable archive.

The download is streamed directly; there is no separate export job status page. The CSV button in the UI exports entities only because entities and audit records do not share one schema.

Configure retention

  1. In Export & Retention, leave a field blank to keep that resource indefinitely.
  2. For Audit log retention (days), enter a whole number from 1 to 3650.
  3. For Telegram history retention (days), enter a whole number from 1 to 3650 only after confirming the deployment supports Telegram pruning.
  4. Select Save.
  5. Reload the page and verify the saved values.

Audit-log retention is applied by a daily sweep, so saving a shorter window does not imply immediate deletion.

Telegram deployment check

The current web UI labels Telegram history retention as Configured-only. Recent worker versions include a Telegram pruning workflow, but older or incompletely scheduled deployments may only save the value. Ask the platform operator to confirm the schedule before promising a deletion deadline.

Verify the result

  • Audit filters return the expected actor and time range.
  • The JSON bundle contains both entities and audit_log; the CSV contains entity columns.
  • Retention fields survive a reload.
  • After the relevant daily sweep, records older than the confirmed window are absent while newer records remain.

Common problems

Symptom Likely cause What to do
Audit Log is missing The owner raised the tab's minimum role Ask the owner to review Organization → Access control
A filter returns nothing Action is exact, the time range is wrong, or the event belongs to another project Clear filters, confirm project and timezone, then narrow again
Export returns 403 Export is admin-only Ask an admin or owner to perform and secure the export
Browser download does not appear The browser blocked it or the request failed Allow the download, retry once, and check the inline error
Old audit entries remain after saving The daily sweep has not run yet Wait for the next confirmed sweep; contact the operator if they remain
Telegram history remains past the value The deployment saved the setting but has no active pruning schedule Ask the operator to verify worker version and schedule before changing policy claims
A deleted record is needed Retention is destructive, not an archive Restore only from an approved export or backup through the operator process

Next step

Apply the security and access checklist and review role permissions.