Directory privacy audit log reference
This page describes the columns in the directory privacy audit log and explains how to read and export it.
The audit log is available on any member’s detail page under the Privacy audit tab. It records every directory privacy change for that member, whether the member made the change themselves or an admin applied it. To open the audit log, see Audit member directory privacy changes.
Audit log columns
Section titled “Audit log columns”The Privacy audit tab shows three columns:
| Column | What it shows |
|---|---|
| Timestamp | When the change was recorded |
| Change | The event type, then the category, then any note, separated by “ · “ — for example opt out · directory (the member left the directory listing) or opt in update (a field’s visibility changed while the member was listed) |
| Source | How the change was made: member_self_service (the member changed it themselves) or admin_override (an admin applied privacy defaults) |
The exported CSV has more columns (see Exporting the audit log below). For directory privacy changes, its Policy version, IP address and User agent columns are empty: they aren’t recorded.
Admin-initiated change rows
Section titled “Admin-initiated change rows”A row written when an admin applies privacy defaults to existing members (or undoes that) has Source admin_override. In the CSV, its Admin user ID column holds the ID of the admin who made the change; the tab doesn’t show it. No per-row reason is recorded: the reason the admin chose is kept with that update, not on each member’s row.
For the full list of reason codes, see Privacy override reason codes reference.
Exporting the audit log
Section titled “Exporting the audit log”Select Export CSV on the Privacy audit tab to download the member’s whole log as privacy-audit-<member ID>.csv, newest first. It needs the same permission as the tab (member:view-privacy-audit).
| CSV column | What it holds |
|---|---|
| Timestamp | When the change happened (occurredAt, ISO 8601 UTC) |
| Event | What happened (eventType, for example opt_out) |
| Category | The privacy category the change applies to |
| Note | The note recorded with the change, if any |
| Source | How the change was made (source, for example admin_override) |
| Policy version | The privacy policy version in effect |
| Admin user ID | The admin who made the change, for admin changes |
| IP address, User agent | The device details at the time of the change |
| Event ID | The audit row’s own ID |
A cell that starts with =, +, - or @ is written with a leading ' so a spreadsheet shows it as text instead of running it as a formula.
An export holds up to 1,000 rows. A longer log is not cut short: nothing downloads and you see “This member has more than 1,000 privacy changes — more than one CSV download holds. Nothing was downloaded.” The export never goes to your export history, and no email or notification is sent.
Rollback
Section titled “Rollback”If an update that applied privacy defaults to existing members needs to be reversed, select Undo on the “Privacy defaults applied to {N} members” message that the Privacy defaults page shows right after the update. The Undo appears only on that message and is gone once you leave the page — no other screen can undo the update. Each member the undo changes gets a new row; the original rows stay. [amended pre-merge 2026-10-17, c21 BD r2: this said the Undo could be selected “within 48 hours”.] (v1.1, 2026-10-17: this said “Contact your organization’s primary admin to initiate a rollback.”)