---
title: "Audit Logging"
description: "What RIKAISO records, how long entries are kept, and how to export them."
source: "https://help.rikaiso.com/2025.2/audit-logging"
version: "2025.2"
latest: false
language: "en"
section: "Administration"
updated: "2026-09-01"
---

# Audit Logging

> What RIKAISO records, how long entries are kept, and how to export them.

## Recorded events

The audit log is append-only. Entries cannot be edited or deleted by any tenant role, including `admin`.

| Category | Examples |
| --- | --- |
| Authentication | Sign-in, failed sign-in, sign-out |
| Access management | Invitation created or revoked, role granted |
| Content | Draft saved, content published, content imported |
| Privacy | Consent record exported, consent lookup |
| Integration | API key created, API key revoked, API write |

## Entry contents

Each entry stores the action, a human-readable summary, the acting identity, the acting email address where available, and a timestamp in UTC. Business payloads are never copied into the log; the summary references the record instead.

## Viewing and exporting

1. Open **Administration → Audit log**. The 100 most recent entries load immediately.
2. Filter by action or period.
3. Select **Export** for a CSV of the filtered range. Exports above 50,000 rows are delivered as a download link by email.

## Retention

Audit entries are retained for 24 months, independent of the retention schedule that applies to business records. Deleting a user does not remove their audit history; the identity is replaced with a stable pseudonym.

> Integration writes are attributed to the API key name, not to a person. Name your keys after the system that uses them, for example `ci-bot` or `docs-sync`.