Skip to content

DocsOrganizations

OpenPulse

Organizations

Audit log

An append-only log of who did what, chained by hash, with export, a chain check and legal hold.

Built Every organization has an append-only log of who did what: members, roles, invitations, groups, departures, sign-ins to its apps, approvals and changes to its setup. Open it in the Console under Audit log. The owner, admins and auditors can read it.

What an event holds#

FieldMeaning
seqIts place in your organization’s log.
atWhen the directory wrote it. This time always rises with seq.
occurred_atWhen it happened, as its sender says. A time more than five minutes past arrival is stored as the arrival time.
actor_didWho did it.
actionWhat happened, for example member.deprovisioned or signin.refused.
targetWhat it happened to, where there is one.
detailFurther facts about the event.
hashThe SHA-256 hash that chains it to the event before.

Filter and export#

Filter by kind of event, by day and by who did it. An export writes everything the filters match as CSV or JSON, up to 200,000 events at a time. Narrow the dates to export more. A CSV cell that a spreadsheet would run as a formula is neutralized.

Verify the chain#

Each event's hash covers the hash of the event before it and the event's own fields, so a changed or missing event breaks the chain. The database refuses to update an event, and refuses to delete one before its year is up.

  1. Run the check

    Press Verify the chain. It recomputes every event from the oldest one kept.
  2. Keep the newest hash

    An intact chain names its newest event and that event's hash. Store both outside OpenPulse.
  3. Compare later

    Run the check again and find your stored event in an export. If the chain is intact and the event still has the same hash, nothing before it changed.

A break names the event where the chain fails. If the log cannot be read, the check reports an error and never reports an intact chain.

Events are kept for one year and then removed. Once the oldest events are gone, the check starts from the oldest event kept. The owner can set a legal hold with a reason, such as a case number. While a hold is set, no event of the organization is removed. Setting and lifting a hold are both written to the log.