Audit log

Check afterwards what happened

Important actions such as sign-ins, permission changes, deletions and Security Filter hits are recorded. The text of conversations is not.

What is recorded

Who, when and what

The person, the time, the kind of action and the result. More than 160 kinds of events are covered, including authentication, permission changes, deletions, artifact operations and billing.

Security Filter hits

The kind and number of hits, the action and the rule ID are recorded. The matched value itself is not.

Legal Hold and deletion records

Turning Legal Hold on or off, a deletion that was blocked, and the deletion of personal data are recorded too.

How to search

It is under Audit Log in Settings, for organization admins.

01

Filter on screen

Filter by period, kind of event and person. The list also shows each record's retention level (Tier).

02

Ask the AI

Ask something like "show me this month's Legal Hold events" and the AI sets the period and kind filters. The AI is not given the contents of the records, only your question and the filter fields.

How long records are kept (three tiers)

The more important the record, the longer it stays and the stronger the tamper detection.

項目RetentionTamper detectionTypical records
Tier 17 yearsHash chainSign-ins, permission changes, personal data deletion, Legal Hold on and off, contract changes
Tier 21 year (7 years for Enterprise anomaly records)—Security Filter hits, team operations, refused attempts to delete personal data
Tier 390 days—Everyday actions such as creating conversations or artifacts and running workflows

Tamper detection

Tier 1 records are chained: each one takes in the hash of the one before it. If a record is later changed or removed, the chain no longer lines up. Our team verifies the chain. Tamper detection is standard from Business upward.

After seven years

Tier 1 records are kept for seven years, and only records older than that are deleted by our team, following a set procedure. Before deleting, the whole chain must pass verification, and records are removed only as an unbroken run from the oldest end, never from the middle. After a deletion, the hash of the last record removed is kept as an anchor so verification stays unbroken. Records of an organization under Legal Hold are not deleted.

What admins cannot see

  • The text of members' conversations and the AI's replies. Admins have no standing permission to read them. The risk view on the organization dashboard is also built from record types and counts, not from text.
  • The values the Security Filter matched.
  • Records of other organizations.

What it cannot do yet

The "All events" list cannot be saved as a file, and there is no automatic forwarding to a SIEM.

What you can save as a file

Security Filter records can be saved as CSV by an organization admin from Settings › Audit Log › Security Filter, using "Export CSV" (Business+ and above). The range you have filtered on screen is what is saved, and each time it is saved, that is recorded in the audit log too. The file holds the time, person, result, kind and number of hits, rule name and similar fields; it never contains the matched values or the conversation text. A single file has a row limit; if it is exceeded the file stops partway, so narrow the period.

Enterprise is available online: choose your seats and shared PFC, then pay by card.

Go to the sign-up page
Language日本語English